Hello,
Apologies if this is duplicated elsewhere. I did post yesterday, but I cannot now trace the entry.
I have a database with a back end on a server and front ends on client pc's. It is written in Access 2000.
I have been asked to upgrade to Access 2002.
On help from Microsoft, they advise: "The best way to convert your secured Microsoft Access application is possible only if you remembered to write down your Workgroup ID (WID) and Personal ID's (PID) when you created your original secured workgroup information file.
You can create a new workgroup file in the latest version of Microsoft Access by inputting those exact strings. Then, when you convert your database, you are ready to go. "
I have done this, joined the new workgroup, and then tried to upgrade. I am advised that I do not have permissions.
I can upgrade using the old workgroup file, but as Microsoft mention, you will be unable to take advantage of any new functionality that may have been added to user-level security in the latest version of Microsoft Access.
As the database is split, do I need to de-secure, consolidate to one database (ie not split), convert to 2002 and then re-secure.
Can someone point me in the right direct regarding upgrading a split database from 2000 to 2002.
Thank you and regards...Adam
EXTRACT FROM MICROSOFT:
WHAT'S THE BEST WAY TO CONVERT MY SECURED MICROSOFT ACCESS APPLICATION TO THE LATEST VERSION OF MICROSOFT ACCESS?
The best way to convert your secured Microsoft Access application is possible only if you remembered to write down your Workgroup ID (WID) and Personal ID's (PID) when you created your original secured workgroup information file.
You can create a new workgroup file in the latest version of Microsoft Access by inputting those exact strings. Then, when you convert your database, you are ready to go.
If you can't re-create your workgroup information file, you can run a Microsoft Access database against an earlier version's workgroup file. However, you will be unable to take advantage of any new functionality that may have been added to user-level security in the latest version of Microsoft Access.
Your best bet is to "de-secure" the application in the older version of Microsoft Access before converting it (grant full permissions to the Users group and put the Admin user back in Admins, clearing its password), as mentioned in Section 36, “How can I 'de-secure' a database?”
Convert the de-secured application, and then re-secure it in the current version of Microsoft Access, using the steps discussed in Section 1, “What are the steps to secure a database?”
Apologies if this is duplicated elsewhere. I did post yesterday, but I cannot now trace the entry.
I have a database with a back end on a server and front ends on client pc's. It is written in Access 2000.
I have been asked to upgrade to Access 2002.
On help from Microsoft, they advise: "The best way to convert your secured Microsoft Access application is possible only if you remembered to write down your Workgroup ID (WID) and Personal ID's (PID) when you created your original secured workgroup information file.
You can create a new workgroup file in the latest version of Microsoft Access by inputting those exact strings. Then, when you convert your database, you are ready to go. "
I have done this, joined the new workgroup, and then tried to upgrade. I am advised that I do not have permissions.
I can upgrade using the old workgroup file, but as Microsoft mention, you will be unable to take advantage of any new functionality that may have been added to user-level security in the latest version of Microsoft Access.
As the database is split, do I need to de-secure, consolidate to one database (ie not split), convert to 2002 and then re-secure.
Can someone point me in the right direct regarding upgrading a split database from 2000 to 2002.
Thank you and regards...Adam
EXTRACT FROM MICROSOFT:
WHAT'S THE BEST WAY TO CONVERT MY SECURED MICROSOFT ACCESS APPLICATION TO THE LATEST VERSION OF MICROSOFT ACCESS?
The best way to convert your secured Microsoft Access application is possible only if you remembered to write down your Workgroup ID (WID) and Personal ID's (PID) when you created your original secured workgroup information file.
You can create a new workgroup file in the latest version of Microsoft Access by inputting those exact strings. Then, when you convert your database, you are ready to go.
If you can't re-create your workgroup information file, you can run a Microsoft Access database against an earlier version's workgroup file. However, you will be unable to take advantage of any new functionality that may have been added to user-level security in the latest version of Microsoft Access.
Your best bet is to "de-secure" the application in the older version of Microsoft Access before converting it (grant full permissions to the Users group and put the Admin user back in Admins, clearing its password), as mentioned in Section 36, “How can I 'de-secure' a database?”
Convert the de-secured application, and then re-secure it in the current version of Microsoft Access, using the steps discussed in Section 1, “What are the steps to secure a database?”
