B
Bear
Config: OSX 10.3.9 / Entourage 2004 - all up to date.
Problem: "Error -50" when selecting "Page setup" or "Print" from
Entourage. Does not affect other Office 2004 apps. Started occurring
after a "database rebuild" using the MS Database Utility
Has anyone else worked out a solution to this?
It appears that there is a database corruption that is NOT being fixed
by the MS Database Utility. Even a full rebuild does not fix the
problem (and a database check using the utility indicates that the
database apparently has no problems). The problem is definitely
restricted to the database file, as other database files attached to
other identities (and accessed from the same Entourage app) are not
affected with this error.
Any suggestions??
The only work around I have found is to create a new identity (and
subsequent database file), export all of my data from the corrupted
database as a .rge file, then reimport into the new identity. It works
(ie. you no longer get the -50 error on page setup and print...) but
you lose some information in the export/import process (eg. Contact
groups; Project links; Category settings). So, its not an ideal
workaround...
Desperately need to get a solution to this "feature". Any help greatly
appreciated.
Problem: "Error -50" when selecting "Page setup" or "Print" from
Entourage. Does not affect other Office 2004 apps. Started occurring
after a "database rebuild" using the MS Database Utility
Has anyone else worked out a solution to this?
It appears that there is a database corruption that is NOT being fixed
by the MS Database Utility. Even a full rebuild does not fix the
problem (and a database check using the utility indicates that the
database apparently has no problems). The problem is definitely
restricted to the database file, as other database files attached to
other identities (and accessed from the same Entourage app) are not
affected with this error.
Any suggestions??
The only work around I have found is to create a new identity (and
subsequent database file), export all of my data from the corrupted
database as a .rge file, then reimport into the new identity. It works
(ie. you no longer get the -50 error on page setup and print...) but
you lose some information in the export/import process (eg. Contact
groups; Project links; Category settings). So, its not an ideal
workaround...
Desperately need to get a solution to this "feature". Any help greatly
appreciated.