Bill Wright
Downloads: 0
Posts: 1
Smile Score: +16
About Me
I am a Free member


Visit Stats
Last Visit: 2 years ago
Member Since: 18 May 2011
Profile Views: 564

Bill Wright's Posts
Average Rating from Bill:
(1)

sort: smiles | time
burypromote
+16

wpwright reviewed on 18 May 2011
I have been using DayLite for over a year now. My employer has invested a lot of time into setting up multiple user access to his common data base. We use DayLite for mail integration, project planning, sales tracking, contact data base, i.e. he runs his business off this software. Prior to working for this 5 person organization I was in a larger corporate environment, 2,500+ employees with IT and DB staffs using Oracle, SAP and fully supported, robust systems. DayLite from my experience is a powerful application, however we constantly have problems and have to reload the DB. I'm on my 4th re-installation of the application within 1 year. I have never experienced a system so unstable as DayLite. Being an engineer with 20 + years of experience I spoke with other experienced users to see if possibly if we were the problem, might be something on our end we were doing to cause the issues. One of my resources began working with Apple in its early days and is considered one of the top Apple consultants in the Dallas area. Several years ago she had 3 or 4 consultants that worked for her that wrote custom applications for her clients using DayLite. All of these consultants have moved away from DayLite due to the issues with this platform. I asked what is the issue and here's what I was told. DayLite was developed as a standalone, single user application and modified to work as a multiuser application versus being designed from the ground up as a multiuser application. I understand from other users it works fine as single user system. It seems to work OK if as multiuser system if one works off the live DB (shared), however you might as well go make a sandwich and come back each time you hit the live DB (10-30 second lag or longer). Yes, we tested our DNS and the quality of our connections (2 Mbps up/ 25 Mbps down). To make DayLite work due to this lag, each user has to work of their own "Offline" DB and we have it set to synch with the live DB every 5 minutes. According to my Apple consultant, this is a sign of a poorly designed DB. There are other DB's you can work off (live) from one's remote location that don't have this type of lag, which should tell one, there is an issues with DayLite. Synching is the last method one should employee to work with a DB. You are setting yourself up for corruption of your DB, which has happened with us more than once. On one occasion our synching caused the DB to duplicate records throughout the DB multiple times. With over 7,000 contact with mail integration, it took my employer several weekends, hundreds of hours to clean out the DB. He tried reloading the DB from an older copy and that failed as well. Right now I'm working of MY PC as DayLite on my Apple is being re-installed (offline DB) for the 5th time. It has been running now for 1 entire day, which is what is required. Getting back to my Apple consultant, all her clients have moved off the platform due to the reasons I'm having to live through with my current position. I next checked the web and found an attorney who had a DayLite blog, but noticed there weren't any postings from him on his blog since 2008. I contacted this attorney and he moved off the platform to cloud computing. DayLite required a lot of attention to maintain the data base and his server and he believed it was older technology and moved to cloud computing where someone else took care of these problems. Checking DayLite out myself out, they advertise 10 years, 28 employees, and customers in over 100 countries. My 1st question is how could 28 employees support a DB if it has a large user groups in 100 countries? Wouldn't they be stretched trying to support that many users? From my experience it is difficult to get help from DayLite with issues. My employer in now on his 2nd DayLite consultant.

My advice, if you are a single user, probably OK but with one of the top Apple consultants warning me about using this and spending probably 10% of my time fighting this DB and loosing time, I would not recommend using this as multiuser platform in synch mode. After having worked with Oracle and other robust platforms, if you're from a similar environment, do your homework before making the decision to use this DB. There is a reason why some very talented and exceptionally sharp professionals have moved away from this platform. Just my opinion.
[Version 3.13]



There are currently no troubleshooting comments by this member.

Displaying 1-1 of 1
Please login or create a new
MacUpdate Member account
to use this feature


- -