Question: What are Act! DBFixers and where can I find them?
Product Details:
Product Family: Act!
Product: Act! Pro, Act! Premium
Version: 2005, 2006, 2007, 2008, 2009, v16, v18, v19
Answer:
Act! DBFixer files are used to correct issues discovered in the program after it has been released. Below is a list of versions of Act! which have DBFixers which are applicable to them. You can click any of the versions in the list below to be taken to a section that lists out a short description of each DBFixer file, as well as a link to a knowledgebase article specifically for that issue.
Act! v19
Return to Top
Act! v18
Return to Top
Act! v17
Return to Top
Act! v16
Return to Top
ACT! by Sage 2010
Return to Top
ACT! by Sage 2009
Return to Top
ACT! by Sage 2008
Return to Top
ACT! by Sage 2007
Return to Top
ACT! by Sage 2006
Return to Top
ACT! by Sage 2005
Return to Top
Product Details:
Product Family: Act!
Product: Act! Pro, Act! Premium
Version: 2005, 2006, 2007, 2008, 2009, v16, v18, v19
Answer:
Act! DBFixer files are used to correct issues discovered in the program after it has been released. Below is a list of versions of Act! which have DBFixers which are applicable to them. You can click any of the versions in the list below to be taken to a section that lists out a short description of each DBFixer file, as well as a link to a knowledgebase article specifically for that issue.
- Act! v19
- Act! v18
- Act! v16
- ACT! by Sage 2010
- ACT! by Sage 2009
- ACT! by Sage 2007
- ACT! by Sage 2006
- ACT! by Sage 2005
Act! v19
| Timeless activities from v16 and older display incorrectly and cannot be cleared after updating to a newer version of Act! | Timeless activities from v16 and older display incorrectly and cannot be cleared after updating to a newer version of Act! Answer ID Timeless activities from v16 and older display incorrectly and cannot be cleared after updating to a newer version of Act! |
Return to Top
Act! v18
| Timeless activities from v16 and older display incorrectly and cannot be cleared after updating to a newer version of Act! | Timeless activities from v16 and older display incorrectly and cannot be cleared after updating to a newer version of Act! Answer ID Timeless activities from v16 and older display incorrectly and cannot be cleared after updating to a newer version of Act! |
| When renaming a Yes/No field, the new name does not save and reverts back to the original field name. | Yes/No fields unable to be renamed in Act! Answer ID Yes/No fields unable to be renamed in Act! |
| Unable to login to a remote database that was created when using syncset criteria | Error: “Could not authenticate user. Verify the name and password, and try again.” when logging into a remote database that has syncset criteria defined Answer ID Error: “Could not authenticate user. Verify the name and password, and try again.” when logging into a remote database that has syncset criteria defined |
Return to Top
Act! v17
| Timeless activities from v16 and older display incorrectly and cannot be cleared after updating to a newer version of Act! | Timeless activities from v16 and older display incorrectly and cannot be cleared after updating to a newer version of Act! Answer ID Timeless activities from v16 and older display incorrectly and cannot be cleared after updating to a newer version of Act! |
Return to Top
Act! v16
| When updating fields that are linked between Companies and Contacts, some of the linked fields are not updated | Linked Fields Between Contacts and Companies Are Not Updating Properly Answer ID Linked Fields Between Contacts and Companies Are Not Updating Properly Linked Fields between Contacts and Companies are not updating properly Answer ID Linked Fields between Contacts and Companies are not updating properly |
| Queries on custom tables and fields will fail until ActDiag repairs have run | Custom tables and fields in those tables require ActDiag OLEDB repair Answer ID Custom OLEDB tables and fields in those tables require ActDiag OLEDB repair |
| If company creation is enabled, Contacts who have Company names will not synchronize between remote and main databases | Contacts with company names will not sync with company creation enabled Answer ID Contacts with company names will not sync with company creation enabled |
Return to Top
ACT! by Sage 2010
| When attempting to synchronize a remote database, an error appears: “Converting datatype int to tinyint” | Error: "Converting datatype int to tinyint" Answer ID Error: "Converting datatype int to tinyint" |
Return to Top
ACT! by Sage 2009
| After synchronizing the remote database, data does not transfer properly from the main database to the remote database | Data is Not Transferring Properly During Synchronization Answer ID Data is Not Transferring Properly During Synchronization |
| When updating fields that are linked between Companies and Contacts, some of the linked fields are not updated | Linked Fields Between Contacts and Companies Are Not Updating Properly Answer ID Linked Fields Between Contacts and Companies Are Not Updating Properly |
| When attempting to synchronize a remote database, an error appears: “Converting datatype int to tinyint” | Error: "Converting datatype int to tinyint" Answer ID Error: "Converting datatype int to tinyint" |
| Activities that were cleared in ACT! 3.x, 4.x, 5.x (2000), or 6.x (2004) are no longer cleared after converting to ACT! by Sage 2009 | Cleared Activities Become Uncleared After Converting from ACT! 3.x, 4.x, 5.x (2000) or 6.x (2004) to ACT! by Sage 2009 (11.1) Answer ID Cleared Activities Become Uncleared After Converting from ACT! 3.x, 4.x, 5.x (2000) or 6.x (2004) to ACT! by Sage 2009 (11.1) |
Return to Top
ACT! by Sage 2008
| After synchronizing the remote database, data does not transfer properly from the main database to the remote database | Data is Not Transferring Properly During Synchronization Answer ID Data is Not Transferring Properly During Synchronization |
| When updating fields that are linked between Companies and Contacts, some of the linked fields are not updated | Linked Fields Between Contacts and Companies Are Not Updating Properly Answer ID Linked Fields Between Contacts and Companies Are Not Updating Properly |
| Attempting to open a report results in the Error: “Field Not Found” or “Missing Field” | Error: "Field Not Found" or "Missing Field" Answer ID Error: "Field Not Found" or "Missing Field" |
| When attempting to synchronize a remote database, an error appears: “Converting datatype int to tinyint” | Error: "Converting datatype int to tinyint" Answer ID Error: "Converting datatype int to tinyint" |
Return to Top
ACT! by Sage 2007
| When attempting to synchronize a remote database, an error appears: “Converting datatype int to tinyint” | Error: "Converting datatype int to tinyint" Answer ID Error: "Converting datatype int to tinyint" |
Return to Top
ACT! by Sage 2006
| After creating a remote database, the Finish button is grayed out and no .RDB file is created | No .RDB File Exists After Creating a Remote Database or the Finish Button is Grayed Out Answer ID No .RDB File Exists After Creating a Remote Database or the Finish Button is Grayed Out |
| Attempting to create a copy of a database after updating results in the Error: “The specified location for you copy database is invalid. A database must be copied on a drive on your machine." | Error: "The specified location for your copy database is invalid. A database must be copied on a drive on your machine." When Attempting To Create a Copy After Updating ACT! Answer ID Error: "The specified location for your copy database is invalid. A database must be copied on a drive on your machine." When Attempting To Create a Copy After Updating ACT! |
| Attempting to create a remote database after updating Act! produces the Error: "Failed to create remote database [Database_Name] could not alter table [Table_Name] BECAUSE THIS TABLE DOES NOT EXIST IN DATABASE [Product_Code] PRC_UTIL_CREATEINDEXESKEYS:FOREIGN KEY" | Error: "Failed to create remote database [Database_Name] could not alter table [Table_Name] BECAUSE THIS TABLE DOES NOT EXIST IN DATABASE [Product_Code] PRC_UTIL_CREATEINDEXESKEYS:FOREIGN KEY" Answer ID Error: "Failed to create remote database |
| Contacts which are imported into the database after enabling synchronization do not synchronize | Imported or Re-imported (Merged) Contacts Do Not Synchronize Answer ID Imported or Re-imported (Merged) Contacts Do Not Synchronize |
| When attempting to synchronize a remote database, an error appears: “Converting datatype int to tinyint” | Error: "Converting datatype int to tinyint" Answer ID Error: "Converting datatype int to tinyint" |
| Attempting to synchronize the remote database results in the Error: "["Date" "Time" ] Failed to synchronize with the server. Server Error Description: The identifier that starts with 'CUST_Startdate3rdcontr_015245 FROM dbo.CTL_SYNCROW_UPDATE SRU INNER JOIN dbo.TBL_CONTACT SRC ON SRU.ROWID1... | Error: "["Date" "Time" ] Failed to synchronize with the server. Server Error Description: The identifier that starts with 'CUST_Startdate3rdcontr_015245 FROM dbo.CTL_SYNCROW_UPDATE SRU INNER JOIN dbo.TBL_CONTACT SRC ON SRU.ROWID1... Answer ID Error: "["Date" "Time" ] Failed to synchronize with the server. Server Error Description: The identifier that starts with 'CUST_Startdate3rdcontr_015245 FROM dbo.CTL_SYNCROW_UPDATE SRU INNER JOIN dbo.TBL_CONTACT SRC ON SRU.ROWID1... |
| Attempting to synchronize a remote database produces the Error: "Failed to synchronize with the server. Server Error Description: Incorrect syntax near the keyword "FROM". Contact your administrator for assistance." | Error: "Failed to synchronize with the server. Server Error Description: Incorrect syntax near the keyword "FROM". Contact your administrator for assistance." Answer ID Error: "Failed to synchronize with the server. Server Error Description: Incorrect syntax near the keyword "FROM". Contact your administrator for assistance." |
Return to Top
ACT! by Sage 2005
| After creating a remote database, the Finish button is grayed out and no .RDB file is created | No .RDB File Exists After Creating a Remote Database or the Finish Button is Grayed Out Answer ID No .RDB File Exists After Creating a Remote Database or the Finish Button is Grayed Out |
| Attempting to create a copy of a database after updating results in the Error: “The specified location for you copy database is invalid. A database must be copied on a drive on your machine." | Error: "The specified location for your copy database is invalid. A database must be copied on a drive on your machine." When Attempting To Create a Copy After Updating ACT! Answer ID Error: "The specified location for your copy database is invalid. A database must be copied on a drive on your machine." When Attempting To Create a Copy After Updating ACT! |
| Attempting to create a remote database after updating Act! produces the Error: "Failed to create remote database [Database_Name] could not alter table [Table_Name] BECAUSE THIS TABLE DOES NOT EXIST IN DATABASE [Product_Code] PRC_UTIL_CREATEINDEXESKEYS:FOREIGN KEY" | Error: "Failed to create remote database [Database_Name] could not alter table [Table_Name] BECAUSE THIS TABLE DOES NOT EXIST IN DATABASE [Product_Code] PRC_UTIL_CREATEINDEXESKEYS:FOREIGN KEY" Answer ID Error: "Failed to create remote database |
| Attempting to synchronize the remote database results in the Error: "["Date" "Time" ] Failed to synchronize with the server. Server Error Description: The identifier that starts with 'CUST_Startdate3rdcontr_015245 FROM dbo.CTL_SYNCROW_UPDATE SRU INNER JOIN dbo.TBL_CONTACT SRC ON SRU.ROWID1... | Error: "["Date" "Time" ] Failed to synchronize with the server. Server Error Description: The identifier that starts with 'CUST_Startdate3rdcontr_015245 FROM dbo.CTL_SYNCROW_UPDATE SRU INNER JOIN dbo.TBL_CONTACT SRC ON SRU.ROWID1... Answer ID Error: "["Date" "Time" ] Failed to synchronize with the server. Server Error Description: The identifier that starts with 'CUST_Startdate3rdcontr_015245 FROM dbo.CTL_SYNCROW_UPDATE SRU INNER JOIN dbo.TBL_CONTACT SRC ON SRU.ROWID1... |
| Attempting to synchronize a remote database produces the Error: "Failed to synchronize with the server. Server Error Description: Incorrect syntax near the keyword "FROM". Contact your administrator for assistance." | Error: "Failed to synchronize with the server. Server Error Description: Incorrect syntax near the keyword "FROM". Contact your administrator for assistance." Answer ID Error: "Failed to synchronize with the server. Server Error Description: Incorrect syntax near the keyword "FROM". Contact your administrator for assistance." |
Return to Top