Issue: Yes/No fields unable to be renamed in Act!
Version Found: 18.0.4
Steps to Reproduce
Actual Result:
The field's new name does not save and reverts back to the original name.
Solution:
Important Note:This DBFixer only needs to be applied to master copies of an Act! database, and not Remote Databases used to sync with a Master Database.
It is strongly recommended that you create a backup of your main database before proceeding with this workaround. For instructions on creating a backup of your database, refer to the following knolwedgebase article:
How to back up and restore an Act! database
Answer ID How to back up and restore an Act! database
Follow the steps below to run the DBFixer
Note: If you have are upgrading Act! from a version prior to v18.0, you MUST open your database after the installation has completed and follow the prompts to allow it to update to v18 before proceeding with the steps below. This DBFixer will not work until the database itself has been updated to Act! v18.0
Reference #: D-04033, D-04035
Status: Closed, Fixed in v18.0 Hotfix 5
Related information:
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
If you have just installed Act! 18.0 or applied an update to Act! v18.0, please read on.
This KB article lists additional steps for database owners to complete the installation of Act! v18.0 or complete the application of an update to Act! v18.0. If you do not manage any Act! Databases personally, these instructions do not apply to you. You may wish to discuss this article with your Act! database administrator if you have any questions.
If you do manage one or more Act! databases on your computer, and you haven't yet applied the Act! DBFixer attached to this article, please look below for instructions on the installation and use of the attached DBFixer tool to complete the installation of Act! v18.0 or any applied updates.
This KB article lists additional steps for database owners to complete the installation of Act! v18.0 or complete the application of an update to Act! v18.0. If you do not manage any Act! Databases personally, these instructions do not apply to you. You may wish to discuss this article with your Act! database administrator if you have any questions.
If you do manage one or more Act! databases on your computer, and you haven't yet applied the Act! DBFixer attached to this article, please look below for instructions on the installation and use of the attached DBFixer tool to complete the installation of Act! v18.0 or any applied updates.
Version Found: 18.0.4
Steps to Reproduce
- Login to an Act! database as an Administrator
- Click Tools > Define fields
- Create a new Yes/No field
- After creating the field, go back and attempt to rename the field
Actual Result:
The field's new name does not save and reverts back to the original name.
Solution:
Important Note:This DBFixer only needs to be applied to master copies of an Act! database, and not Remote Databases used to sync with a Master Database.
It is strongly recommended that you create a backup of your main database before proceeding with this workaround. For instructions on creating a backup of your database, refer to the following knolwedgebase article:
How to back up and restore an Act! database
Answer ID How to back up and restore an Act! database
Follow the steps below to run the DBFixer
Note: If you have are upgrading Act! from a version prior to v18.0, you MUST open your database after the installation has completed and follow the prompts to allow it to update to v18 before proceeding with the steps below. This DBFixer will not work until the database itself has been updated to Act! v18.0
- On the main computer where the database files are stored, ensure that Act! is closed
- Download and save the DBFixer found in the File Attachments section of this article
- Once downloaded, double-click the DBFixer to launch it
- When prompted, read the disclaimer, then click OK
- From the Database Name drop-down, select the name of the database, then click Apply Fix
- When the notification of completion appears, click OK,
- Repeat for each master database in the drop-down menu.
- Click Close to close the DBFixer Utility
- Attempt to rename the Yes/No field again to verify the fix
Reference #: D-04033, D-04035
Status: Closed, Fixed in v18.0 Hotfix 5
Related information:
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