07-21-2009 01:54 PM
07-23-2009 06:19 AM
Greig Hollister
Note: Effective 6/1/13, Sage no longers provides support for the Act! software. This is now provided by Swiftpage.
07-23-2009 06:45 AM
Yes - for all remote users. Some further information: I am looking at the tables through ACT READER and note:
Jim
07-23-2009 08:57 AM
Has this issue always occurred, or did it correspond with an update to ACT!?
One suggestion would be to run maintenance on the Publisher database, create a new remote database and test sync. Do the following on the Publisher database:
- In ACT!, go to Tools/Database Maintenance/Check & Repair...run twice in a row
- Close ACT!
- Open ACT! Diagnostics by typing actdiag in the Run box from the Start menu
- In ACT! Diagnostics, select Databases, then Database List and highlight the Publisher database on the list
- Right-click on the database and run the following maintenance items, in this order:
Database Fixes/Schema Update/Fix Known Schema Update Issues
Database Rebuilds/Rebuild Schema
Database Rebuilds/Rebuild Sync Objects
Reindex
You can also try running this same process on one of the remotes and testing sync. You can also determine if this is database-specific by opening the demo database (ACT11Demo), enabling sync, creating a remote and syncing (you will need to add the Demo to your sync service if using Network Sync).
Greig Hollister
Note: Effective 6/1/13, Sage no longers provides support for the Act! software. This is now provided by Swiftpage.
07-23-2009 09:03 AM
This began after we upgraded from 2005 to 2009 of ACT.
07-24-2009 07:50 AM
Greig Hollister
Note: Effective 6/1/13, Sage no longers provides support for the Act! software. This is now provided by Swiftpage.