04-14-2010 04:03 PM
I decied to get a new lauptop. I purchased a DELL with Windows 7. I tried to install my ACT! 2000 disc to no avail. Now what do I do?
04-14-2010 05:40 PM
04-15-2010 05:54 AM
04-15-2010 06:26 AM
The latest release of Act! (2010 - V12) is fully Vista and Windows7 compatible. Your Act! 2000 database can be converted in it's entirety to the new format.
As reference, here are some informational links:
04-15-2010 09:44 AM
04-20-2010 07:49 AM
Message moved to appropriate Board for better exposure.
05-06-2010 09:24 AM
05-06-2010 09:56 AM
That is correct, Act! 2010 will not restore a backup file created with Act! 2000 because of the differing database/backup structures. To access and update your Act! 2000 database into the Act! 2010 program:
- copy the zip file from the disk to the local hard drive on the Windows7 computer
- extract the contents of the zip file (create a folder on your C drive called 'Act2000Db' and extract to that location)
- in Act! 2010 > go to Open Database > change the 'Files of Type' to DBF > browse to the folder the database was extracted into and select the DBF file.
- this will begin the conversion wizard
Here is a document that more in-depthly explains the conversion process: How to Convert Act 3-6 database to Act! 2010
Before converting your database, it is highly recommended that you run maintenance on your Act! 2000 database. The instructions for this are included in the attached link. You will then need to create a new backup of the database to restore.
05-17-2010 06:41 AM
I'm almost there.
I get down to the stage of converting Notes and Histories and I get the message:
The INSERT conflicted with the FOREING KEY constraint « NOTE_MANAGER_ISERID_FK ». The conflict occurred in database « CAEDT », table « dbo.TBL_ACCESSORID ». The statement has been terminated.
Any idea how to get around this? Thanks
05-18-2010 06:13 AM
This is most likely caused by orphaned records within your V5 database. If you have not already run the database maintenance functions on the database, do so and then attempt to convert again (we recommend running the 'Scan and Repair' step 3 times).
If you have done this and the database is still getting the error during conversion, you will need to import your database into a new database (in V5) so that it can attempt to correct the data.