VirtualKansas
asked on
Access database decompile; getting ready to release for production
Recently read an article describing the following as a finishing touches for an Access database to go to production.
1) Create a new database and import all objects from source database
2) Restart access using /decompile option while holding shift key
a) Restart access normally while holding shift key
i) Close after the database windows is displayed
3) Restart access normally while holding the shift key
4) Compile the database
5) Compact and repair the database
Question is; is this a "good idea"? If so, will this work on a split database, or should it be rejoined before attempting?
1) Create a new database and import all objects from source database
2) Restart access using /decompile option while holding shift key
a) Restart access normally while holding shift key
i) Close after the database windows is displayed
3) Restart access normally while holding the shift key
4) Compile the database
5) Compact and repair the database
Question is; is this a "good idea"? If so, will this work on a split database, or should it be rejoined before attempting?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Pretty much a good idea, but /decompile is an undocumented switch. While it has worked thousands of times, it's also failed and messed up a DB in some cases.
So make sure you have a backup.
Also, if your importing everything into a new DB, you should not need it. When you import, only source code gets pulled.
What /decompile does is invalidate compiled p-code.
Jim.
So make sure you have a backup.
Also, if your importing everything into a new DB, you should not need it. When you import, only source code gets pulled.
What /decompile does is invalidate compiled p-code.
Jim.
ASKER