Newly separated front ends progressively corrupt.

[Mikal via AccessMonster.com]

We have an ADP that was converted from an A97 database maybe 3 or 4 years ago.
Until recently, the lone front end was shared by about 10 users. Corruption
got to be a very large problem in the front end. Recently, each user got his
own individual .ADP. Corruption is still occuring: One of user a's forms
will go bad and his .ADP gets replaced by user b's copy that isn't
experiencing the problem. Then User c gets a different problem and also gets
a new front end. The problem is evidently quite serious, although at least
now there are a multitude of front ends to copy.

All of the front ends were copied from the original lone front end that was
getting beat up for years by itself on the shared drive. Does it seem likely
that this could cause the newly separated .ADP's to progressively corrupt in
this fashion? If not that, then what seems possible?

Thanks in advance.

Mike

 

[Sylvain Lafontaine]

Decompile each front end after the copy has been made and you should be ok:
use the /decompile switch in a shortcut or add (or remove) a dummy reference
in the VBA window and make a Full Recompile from the Debug menu.

Finish with a Compact /Repair from the database tools menu.

 

[Mikal via AccessMonster.com]

That is a bit over my head. I'll search around and see if I can figure it
out and if not, I'll ask for more help. Thank you. You are a fount of
knowledge, sir.

Mike

Decompile each front end after the copy has been made and you should be ok:
use the /decompile switch in a shortcut or add (or remove) a dummy reference
in the VBA window and make a Full Recompile from the Debug menu.

Finish with a Compact /Repair from the database tools menu.

We have an ADP that was converted from an A97 database maybe 3 or 4 years
ago.

[quoted text clipped - 21 lines]

Mike

 

[AkAlan via AccessMonster.com]

Here is what Stephan is refering to. Get a command promt ( Start_Run ) then
enter the following line replaceing info with your own path to Access. The
first part opens Access so you need to know where it is on your machine. The
/decompile is the switch and then the path to the project you need to fix.
This has worked for me very well for the types of problems you are having.
Good Luck.


"C:\Program Files\Microsoft Office\OFFICE11\msaccess.exe" /decompile "C:\
Documents and Settings\alan.fisher\Desktop\Sample.adp"

That is a bit over my head. I'll search around and see if I can figure it
out and if not, I'll ask for more help. Thank you. You are a fount of
knowledge, sir.

Mike

Decompile each front end after the copy has been made and you should be ok:
use the /decompile switch in a shortcut or add (or remove) a dummy reference

[quoted text clipped - 7 lines]

 

[Sylvain Lafontaine]

Hi,

Sorry for not having getting back sooner but for unknown reasons (or quite
probably a lot of crap that have crawled into my system these last years),
I've myself some trouble with the decompile option: after having opened the
adp file with this option, I cannot make a Repair/Compact of the database
without first leaving the Access session and opening it again but without
this option.

As this were working perfectly well in the past, I think that this is simply
some kind of problem with my installation.

Finally, if you don't want to use the command line, you can create a shorcut
and use the previous exemple as the target in the properties of the
shortcut.

Also, instead of using the /decompile option, you can click on any module
or event to open the VBA window, open the References window under the Tools
menu and add (or remove) any reference and closing the window. The simple
fact of changing the list of references will force Access to make a
recompilation of all modules. (You can also use the Recompile All modules
under the Debug menu after this but this doesn't prevent you from the
obligation of changing the list of references before to make sure that
Access will effectively recompile all modules.)

Of course, this must be absolutely be done on each target machines and not
on a common source machine.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF

Here is what Stephan is refering to. Get a command promt ( Start_Run )
then
enter the following line replaceing info with your own path to Access. The
first part opens Access so you need to know where it is on your machine.
The
/decompile is the switch and then the path to the project you need to fix.
This has worked for me very well for the types of problems you are having.
Good Luck.


"C:\Program Files\Microsoft Office\OFFICE11\msaccess.exe" /decompile "C:\
Documents and Settings\alan.fisher\Desktop\Sample.adp"

That is a bit over my head. I'll search around and see if I can figure it
out and if not, I'll ask for more help. Thank you. You are a fount of
knowledge, sir.

Mike

Decompile each front end after the copy has been made and you should be
ok:
use the /decompile switch in a shortcut or add (or remove) a dummy
reference

[quoted text clipped - 7 lines]

Mike

 

[dbahooker]

I've had problems like this.. when I've had one desktop that points to
a wierd label printer or something.. that's just when you launch
reports though

-aaron

Hi,

Sorry for not having getting back sooner but for unknown reasons (or quite
probably a lot of crap that have crawled into my system these last years),
I've myself some trouble with the decompile option: after having opened the
adp file with this option, I cannot make a Repair/Compact of the database
without first leaving the Access session and opening it again but without
this option.

As this were working perfectly well in the past, I think that this is simply
some kind of problem with my installation.

Finally, if you don't want to use the command line, you can create a shorcut
and use the previous exemple as the target in the properties of the
shortcut.

Also, instead of using the /decompile option, you can click on any module
or event to open the VBA window, open the References window under the Tools
menu and add (or remove) any reference and closing the window. The simple
fact of changing the list of references will force Access to make a
recompilation of all modules. (You can also use the Recompile All modules
under the Debug menu after this but this doesn't prevent you from the
obligation of changing the list of references before to make sure that
Access will effectively recompile all modules.)

Of course, this must be absolutely be done on each target machines and not
on a common source machine.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF

Here is what Stephan is refering to. Get a command promt ( Start_Run )
then
enter the following line replaceing info with your own path to Access. The
first part opens Access so you need to know where it is on your machine.
The
/decompile is the switch and then the path to the project you need to fix.
This has worked for me very well for the types of problems you are having.
Good Luck.


"C:\Program Files\Microsoft Office\OFFICE11\msaccess.exe" /decompile "C:\
Documents and Settings\alan.fisher\Desktop\Sample.adp"

That is a bit over my head. I'll search around and see if I can figure it
out and if not, I'll ask for more help. Thank you. You are a fount of
knowledge, sir.

Mike

Decompile each front end after the copy has been made and you should be
ok:
use the /decompile switch in a shortcut or add (or remove) a dummy
reference
[quoted text clipped - 7 lines]

Mike

 

[dbahooker]

and for the record; when you go HELP / ABOUT inside _ANY_ office app--
what is the verrsion number??

10.00.324.32423?? give us the whole number.. could even be a mismatched
2000 box without any patches for example that could cause this much
grief

Hi,

Sorry for not having getting back sooner but for unknown reasons (or quite
probably a lot of crap that have crawled into my system these last years),
I've myself some trouble with the decompile option: after having opened the
adp file with this option, I cannot make a Repair/Compact of the database
without first leaving the Access session and opening it again but without
this option.

As this were working perfectly well in the past, I think that this is simply
some kind of problem with my installation.

Finally, if you don't want to use the command line, you can create a shorcut
and use the previous exemple as the target in the properties of the
shortcut.

Also, instead of using the /decompile option, you can click on any module
or event to open the VBA window, open the References window under the Tools
menu and add (or remove) any reference and closing the window. The simple
fact of changing the list of references will force Access to make a
recompilation of all modules. (You can also use the Recompile All modules
under the Debug menu after this but this doesn't prevent you from the
obligation of changing the list of references before to make sure that
Access will effectively recompile all modules.)

Of course, this must be absolutely be done on each target machines and not
on a common source machine.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: http://cerbermail.com/?QugbLEWINF

Here is what Stephan is refering to. Get a command promt ( Start_Run )
then
enter the following line replaceing info with your own path to Access. The
first part opens Access so you need to know where it is on your machine.
The
/decompile is the switch and then the path to the project you need to fix.
This has worked for me very well for the types of problems you are having.
Good Luck.


"C:\Program Files\Microsoft Office\OFFICE11\msaccess.exe" /decompile "C:\
Documents and Settings\alan.fisher\Desktop\Sample.adp"

That is a bit over my head. I'll search around and see if I can figure it
out and if not, I'll ask for more help. Thank you. You are a fount of
knowledge, sir.

Mike

Decompile each front end after the copy has been made and you should be
ok:
use the /decompile switch in a shortcut or add (or remove) a dummy
reference
[quoted text clipped - 7 lines]

Mike