It may not be necessary, but when dealing with a corrupt VB project I prefer to be sure. Regarding step 5: I recommend doing a compact immediately after decompiling, just to be sure that no lingering trace of the compiled VB project is present. I have a shortcut on my desktop for Decompile, which just starts Access with the /decompile switch, allowing me to double-click the shortcut and decompile any database by opening it in Start Access with /decompile and then open it using the Access UI. It doesn't matter whether you specify the name of the database on the command line, or whether you just If you open an Access session with the /decompile command line, the first database opened in that session will be decompiled. I'd either enter the full path and filename of the database after /decompile, or (easier), drag the database from Windows Explorer onto the Run window and drop it in the box where you already have the line mentioned in step 1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |