Re: Problems creating subform
- From: Nikos Yannacopoulos <nyannacoREMOVETHISBIT@xxxxx>
- Date: Mon, 10 Oct 2005 10:08:59 +0300
BruceM wrote:
Thanks for the reply. I was indeed doing a lot of development work. I have learned the value of backups, and perform them as soon as I have incorporated a new element of the database. It helped me in this case.
Good for you! Most of us learned this the hard way!
When you say that it is a good idea to do the former during development, do you mean it is a good idea to decompile and recompile? If so, is theDecompile is run from a comman line prompt, not from within Access / VBA. What it does is, it removes the compiled (executable) code from an ..mdb file. The result is that the next time you run the file, the source code is re-compiled, while you have gotten rid of any executable code rubbish that were left behind during development (deleting the source code for a procedure, or a whole module, doesn't remove its compiled code, I believe).
procedure to enter the following at the command line (all on one line)?
"C:\Program Files\Microsoft Office\Office\msaccess.exe" /decompile "c:\MyPath\MyFile.mdb"
If that is what you meant, do I recompile at a code window or at the command line? By the way, what is compiling and decompiling?
To be honest, I usually just do the "import-into-a-new-mdb" trick, and it does the job just fine. Effectively, it produces the same result, in that compiled code is not carried accross.
I compact and repair during the development process, which as I understand it is a good idea. Do I understand correctly?Definitely a good idea, though not enough. It compacts the data itself (releases unused space from deleted records or even whole tables) and re-indexes the tables, but does not get rid of the executable code garbage. Importing all objects into a new .mdb, on the other hand, does both, to the best of my knowledge. Yet, i still compact and repair all the time during development (it's very fast when there's little data, like the case usually is during development), while I would only create a new copy at the end of the day. For one thing, there's no such thing as one precaution too many!
Nikos .
- References:
- Problems creating subform
- From: BruceM
- Problems creating subform
- Prev by Date: Options for a Report vis Form
- Next by Date: Re: Options for a Report vis Form
- Previous by thread: Problems creating subform
- Next by thread: Re: Problems creating subform
- Index(es):
Relevant Pages
|
