Here is a detailed description with screenshots of how DayLite is causing data (plus time and effort) loss. Hope this helps you avoid data loss.

http://www.imran.com/irate/reviews/DayLiteCausesDataLoss.htm

Imran

Imran

This is a known issue, and is only related to URLs, possibly because the URL field is not, by default, turned on in Address Book, and it’s kind of hard to sync with a field that isn’t there. MC are well aware of the issue and have turned off URL syncing in recent builds until the problem is fixed.

We all know you have had problems with Sync, but it appears that rather than working with MC support, or listening to other people on here—myself included—that have had no issues at all and have tried to help, you would much rather baselessly rubbish a fine product with no just cause. Your experience is not common, tragic though it is.

If the product is not working for you, and not to put to fine a point on it, just **** off. I’m happy to say that because MC obviously won’t.

If you don’t like the product then stop using it. But please cease the incessant whining and complaining posts that are not indicative of the vast majority of users’ experience.

I, for one, would have no problem at all if MC saw fit to ban your sorry *** and removed all your posts. Indeed, I would applaud the move.

My 2c (and most unlike me, but even after counting to ten I was still fuming mad).

Whoa!!! Imram. Take it easy man. I think you are really going overboard here with this holy war against Daylite. I do believe you've had problems, but to assert that the product is such a disaster as you seem to believe is way out of line with reality!

Just because you've encountered some problems, and pointed to some discussions about problems with the latest release does not mean that All, or even many, users are having catastrophic failures or data losses. I know that I am not having any data losses at all and I know that the great majority of users aren't either. I'm also having a nearly perfect experience with syncing and the few bugs that are left are definitely being worked out right now by Marketcircle. I know this because I have been actively beta testing the next release and it has come along very nicely.

The mere existence of a discussion on the forums does not at all represent the experience of the majority of users. When some users have a problem it's obvious that it's they who are the most vocal, and understandably so. But to extrapolate, as you have, that the product is a disaster across the board for all users is simply outrageous and completely untrue.

I do defend your right to express your opinions completely and I am truly sorry if you've had problems. But if you are going to take such an extremely negative, (and in my opinion completely unjustified), position on a public forum such as this, then I am compelled add my voice to Andy's as a counterbalance to what I see as your intent to harm a perfectly amazing and useful product. (Was that a run-on sentence?).

If you are not yet a Daylite user and are reading this, please do give the demo a good test. I believe you will find, as I and the great majority of Daylite users have, it to be a very stable and highly productive CRM that is now making the challenging migration to Leopard and SyncServices. Very shortly there will be a new version released and the problems related to Syncing and Leopard will be taken care of.

BTW, I want to be very clear that I am not a Marketcircle employee and am only writing this as a very satisfied end user who is very concerned that Imram's posts might have an unfair effect on prospective (and even current) users of Daylite. Sorry for the long post, I just felt it was necessary!

Andy, Howard:

Thanks for the much more balanced opinions; I'm far more interested in what members with nearly 200 and 600 posts have to say than a whiner with a measly 17 posts says.

Good god.
A lot of work went into that posting!!

I can't say I agree with the approach Imran is adopting with regards to DL and the problems he's had with it. OTOH, I understand his frustration because I have also been the victim of data loss and general weirdness in DL 3.6.
The developers at marketcircle had ample time to prepare for the release of Leopard, because some of us didn't have a choice but to migrate to the new OS. In my case, I had a developer revamp my filemaker pro database and I needed to run it on the latest Leopard filemaker pro solutions.
I think they (MC) were caught with their proverbial pants down in regards to compatibility of their software with 10.5.Next time, they ought to have something ready before anything hits the fan.

I have had problems galore myself, but now that I can actually connect to my server at home, I won't have to sync with the online database until they get it straightened out.
Furthermore, Address Book is also rife with flakiness itself (in my case, search was broken), so it's not entirely MC's fault. AB was a paragon of stability before Leopard and Apple has screwed with a lot of apps that worked in Tiger and have either stopped working or won't play nice with Leopard.
Personally, I really like Daylite and I can't see running my business without it. I hope and pray that MC will quash the bugs ASAP so that we can all be happy using it instead of argung in the forums

Nicolas

No malice intended, but I have to disagree about your ‘no choice but to migrate’ position.

Apple didn’t release a version of Leopard Gold Master to developers until the same day (the next day?) the shipping version was in the stores, so every developer was in the same position as Marketcircle in that they weren’t 100% sure their software was compatible with the public version until they had time to check.

Further, you say that you had to go to Leopard because your developer had revamped your FileMaker solution and you had to upgrade. I am a registered FileMaker developer and I wouldn’t dream of migrating my clients to Leopard yet; the latest version of FileMaker (9.0) runs perfectly fine on Tiger, as does FM Server.

Indeed, despite the fact that FileMaker is a subsidiary of Apple, they too had issues with the shipping version of Leopard and had to put out an update a few days after its release. Yes, an Apple-owned company could not even have compatible software in advance! In fact, FM server is still not compatible with Leopard. (See the FM/Leopard support page.)

Furthermore—and I keep saying it—version 3.6 is beta, which means you shouldn’t be using it in a mission-critical situation, as it will have known (and unknown) issues that may cause glitches and all sort of oddities.

If you are running a beta of the software, on an uncertified and newly-release version of the OS, you can hardly blame Marketcircle for any issues you may have.

(And I’d talk seriously with your developer as to exactly why you needed to go to Leopard for your FileMaker solution at this stage, as it seems horribly premature, unnecessary and ill-advised to me.)

Cheers

I revamped my FMP solution with the latest version of FMP that is compatible with Leopard.
4 computers at home, 3 at work, all sync with .mac and with eachother and the discussion groups on the Net are clear about how Tiger and Leopard do not play nice with synchronization over .mac.
According to the FMP website, one is supposed to use the same version, latest if possible, of FMP and OS. I'm glad I did because I have zero problems with my database so far.
Furthermore, FMP had its update out weeks before 3.6 was even an idea.
And I didn't blame MC for anything, you're confusing me with someone else.

quote:

discussion groups on the Net are clear about how Tiger and Leopard do not play nice with synchronization over .mac.

I hadn’t heard that; if your solution depends on .Mac, it does indeed make sense to be running the same OS on all machines.

Doesn’t change the fact that you didn’t have to go to Leopard, as the latest FileMaker is just fine on Tiger, and I’d be a little cautious about running a ‘.0’ version of any OS release.

Good to hear you’ve had no problems, but that certainly wouldn’t be the case if you were trying to run the latest FileMaker Server on Leopard, as it simply isn’t yet compatible.

quote:

Furthermore, FMP had its update out weeks before 3.6 was even an idea.

Not quite. The timeline was:

Post to Daylite forums from MC, saying ‘don’t upgrade to Leopard until we announce compatibility: 16th October
Official statement from FileMaker to registered developers that v9 is not compatible: 22nd October
DayLite 3.6 Beta was released to ‘public’ testers: 25th October
Leopard public release date: 26th October
FileMaker release compatibility update for v9 Client: 1st November

In other words, MarketCircle actually told their public users that the shipping version was not compatible before FileMaker told their registered developers, and 3.6 was already in beta and in use by many of us by the time FileMaker had it's update out.

It’s true that a compatible version of Daylite is still not out, but we are nearing that stage, but equally a FileMaker Server update is not scheduled until ‘early 2008’.

I’m still of the opinion that your FileMaker developer was playing a touch fast-and-loose with having you update to the latest OS at this stage, but glad to hear you’ve not had any issues.

quote:

And I didn't blame MC for anything

This sounds somewhat like the laying of blame:

quote:

 
I think they (MC) were caught with their proverbial pants down in regards to compatibility of their software

But I know what you mean, and you certainly don’t seem to be on the same level as Imran.

(P.S. I also note that there is still no news on the cryptic reply to your post re. Daylite and FileMaker of the 1st October!)

Cheers

If you have nothing constructive to add, please do not respond. Whether I should have this or I shouldn't have that is irrelevant.
At this point, since I can connect directly to the database via static ip, I'm happy.

You know, when people ask for help, they don't expect nor want to be patronized or told what they should have done instead of what they did.

And filemaker had a working, practically bug free version of their sw way before Daylite had the dreadful-stopgap beta out. Don't compare Apples and oranges and stop acting like a Daylite fanboy/apologist.

And as usual, no malice intended.

All the emotion on both sides aside, as much as I love Daylite, I have to agree that their new-feature updates are always quite buggy. I've learned the hard way *never* to upgrade until I've monitored the forums for a while to see when the bugs have been worked out -- especially if it's not just a bug-fix release.

You're absolutely correct. Only thing is that I found out about Daylite around the same time the transition towards Leopard was occuring.

And I fail to see where you're seeing a display of emotion from myself. I'm just stating facts

Settle down folks.
The Leopard version will be out soon.

Does anyone else out there feel the need for MC to reimplement url syncing sooner rather than later?
I want DL to remain my main point of data entry, but I also need urls to end up on my iPhone if possible.
This is a realy problem some times for me.