02-11-2009 09:14 AM
02-18-2009 08:34 AM
Based on the information provided, your issue appears to be associated with a previously reported issue.
Error occurs when two user name's first 15 characters match. You can change user names by going to Tools > Manage Users.
02-11-2009 03:20 PM
I would before going much further redo the conversion using the custom option to see if it is in the conversion process
Failing this have you tried doing a file save as and make a copy of the converted database before beginning to enable synchronisation.
02-12-2009 12:29 AM
02-16-2009 05:16 AM
Firstly, exporting the ACT6 database to a CSV file and starting from scratch MAY fix the problem, but it would be the last you ever say of your Notes, History, Opportunities, Groups, etc. What you'd be left with is little more than a table of flat data.
Secondly, I said MAY fix the problem because we have not ruled out the possibility that firewall or security software may be causing this conflict. It's unlikely, but imagine the frustration you'd feel after creating a clean, new database only to encounter the same error message. Try installing ACT! on another computer, and then restore the same database to it to see if you have the same problem. Alternatively, try opening the sample ACT! database and then enabling synchronization. If it crashes then, you know the problem has nothing to do with your database.
Thirdly, after you enabled Synchronization within ACT!, did you enable "Application Sync"; in other words, did you select "Accept Incoming Syncs" from within ACT!? If yes, disable this and then try exiting the program. If it works without error, install Network Sync from the CD as an alternative method.
Fourthly, an effective way of running a simple diagnostic on a potentially corrupt database is to use ACTDiag to "detach" the database, delete the databases PAD file, and then use ACT! to open the same databases ADF file. I used to scoff at this procedure, but after having seen it fix A LOT of databases reporting a variety of errors, I employ this technique at the beginning now.
02-17-2009 06:31 AM - edited 02-17-2009 06:31 AM
02-18-2009 04:12 AM
It sounds like you have isolated it to the database.
If my fourth suggestion does not work, I'd try going back to the ACT6 database and complete some cleanup before you upgrade.
Run some purges on OLD notes and histories that may not be relevant any more - say dates older than four years.
Then remove any sync configurations you may have with the old program.
Once that is completed, run ACTDIAG for that version of your database, and when all tests are successful, try the upgrade again.
02-18-2009 06:54 AM
02-18-2009 07:28 AM
Firstly, never trust the French.
Secondly, I have heard this same "Sage" advice (OK, that was bad), but I've had equal luck upgrading to 2009 as I have to 2008.
I have told many people that were using Foxpro databases older than ACT6, to upgrade to ACT6 before making the SQL upgrade.
Thirdly, I was kidding about never trusting the French.
02-18-2009 07:51 AM
02-18-2009 08:27 AM