There is a problem with number and date fields of databases that have been created on a 68K Macintosh with ClarisWorks 2.x software, then opened on a PowerMacintosh running the native "Accelerated for PowerMacintosh" ClarisWorks 2.1v3 (PPC) application.
The problem has been recreated with number fields that have been defined as a pre-defined input list as well as auto-enter serial numbers.
Symptoms
One example of the problem may be something like this:
Pre-defined list on 68K Macintosh with the values defined as follows:
1
2
3
4
After opening the same file containing the above field on a PowerMacintosh using the native, "Accelerated for PowerMacintosh" version of ClarisWorks 2.1v3, the pre-defined list has been converted to:
1.96875
3.476784003707e-310
5.305232320559e-315
8.095265607109e-320
Again, similar results occur with number fields that are are formatted with the auto-enter option where incrementing by 1 will convert to incrementing by 1.96875.
The inconsistency has also been reported with date fields. When a database file was opened with ClarisWorks PPC running native, the dates in the date field had changed. When the database was opened with non-native ClarisWorks, the dates went back to normal.
Workaround
1. If you see this behavior, close the file immediately without saving changes. (Note, even if you've already saved changes, the following steps may work)
2. Install the 68K version of ClarisWorks 2.1v3 on the Power Macintosh using the installer's Custom install option.
3. Delete or avoid using the Power Macintosh version of ClarisWorks for use with databases.
4. Opening the database with the non-native, 68K version of ClarisWorks will work fine. (TIP: Keep the 68k version, or an alias thereof, on the desktop so your database files can be dragged and dropped over the non-native version of the program to open them.
Claris Engineering is aware of the problem.