Can not import forms

[Guest]

I have a dbase in Access 2003 SP2. It started to crash and I recreated the
master by importing everything and then recreating the tables through a make
table query. Some of the forms didn't look the same and some of the forms
did not retain their code (expressions connected to buttons). I imported one
or two and the code came with. Now I have a form that I try to import, the
screen jumps and the form doesn't appear to be imported. I am not getting an
error message.

Any ideas?

 

[strive4peace]

'~~~~~~~~~ Decompile ~~~~~~~~~

try decompiling the database

make an icon with this as its target:

"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE"
"C:\path\filename.mdb" /decompile

if your Access program is not located in the directory specified, make
the appropriate substitution

after you decompile, compile it if you have any code and then do
compact/repair

'~~~~~~~~~ ~~~~~~~~

you can also make a "generic" decompile icon where the next database you
open will be decomipled...

ie:
"C:\Program Files\Microsoft Office\Office\MSACCESS.EXE" /decompile



Warm Regards,
Crystal
*
have an awesome day
*
MVP Access
Remote Programming and Training
strive4peace2006 at yahoo.com
*

 

[Guest]

I am embarassed but I have never decompiled before. What does that do?

I worked for a few more hours and realized that I had left some of the
system fields in some of the tables. I hope this is what was causing the
problems. I recreated the dbase and reviewed all tables for system fields
and it seems to be working.

Thank you
xine

 

[strive4peace]

Decompile information
---



Hello xine,

these links tell you far more about what decompiling is that I can
don't worry about having never heard of it -- most folks do not know
what it is either


'~~~~~~~~~
Here's what I know about Decompiling:
http://www.rogersaccesslibrary.com/DecompilingDatabases.zip
The document is for Access 97, but it is still essentially correct for
Access 2000.

-- --Roger Carlson MS Access MVP www.rogersaccesslibrary.com
'~~~~~~~~~~

great article (thanks, Tom) -->

* WORKING WITH LARGE PROGRAM DATABASES IN ACCESS 97
from the October 1998 issue of Access/Office/VB Advisor Magazine

http://web.archive.org/web/20030204023622/http://www.databasecreations.com/largedb.htm


'~~~~~~~~~~

Trigeminal Software: The real deal on the /Decompile switch
http://www.trigeminal.com/usenet/usenet004.asp?1033

'~~~~~~~~~~

Decompile or how to reduce Microsoft Access MDB/MDE size and decrease
start-up times
http://www.granite.ab.ca/access/decompile.htm

Unless there is a symptom I'd suggest no more than every month or so for
a front end under active development.

Tony
--
Tony Toews, Microsoft Access MVP
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

'~~~~~~~~~~

In addition to the other links you've been given, check out what Michael
Kaplan says at the following URL ...

http://www.trigeminal.com/usenet/usenet004.asp?1033

Always make a back up copy of your MDB or ADP before using the decompile
switch. It doesn't happen very often, but I have personally seen the
situation where a class module was no longer recognised as a class
module, but appeared to Access and VBA be a standard module, after a
decompile.

-- Brendan Reynolds




Warm Regards,
Crystal
*
have an awesome day
*
MVP Access
Remote Programming and Training
strive4peace2006 at yahoo.com
*