Re: App running Access '97 vs. Access 2K
From: Chris Mills (phad_nospam_at_cleardotnet.nz)
Date: 07/19/04
- Next message: Sarah M: "Re: Database Front / Back end"
- Previous message: Chris Mills: "Re: Covert an application in Access 2000 to Access 2003"
- In reply to: Mark in Miami: "App running Access '97 vs. Access 2K"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 19 Jul 2004 22:57:12 +1200
-A97, though it generally works well, can suffer "corruptions" which may go
unnoticed until you try and convert to a new version (or suffer other
unexplained circumstances). A97 was not actually that stable, only by
comparison to A2k do people think so...
-A2k, I clearly think, is even less stable. General advice is that A2k2 is
more stable. However, the corruption may be in A97.
-Do a full decompile/compile/compact. However, importing to a new database is
considered an even more comprehensive way of "leaving behind corruptions", and
you've already done that.
-You are then faced with debugging to find out what precisely does not work.
We are not to know what the "mysterious code" is! In this case, I'd start
cutting out big portions of the database, then putting it back halves by
smaller halves, until I discover what (halve) is causing the problem. Yes I
have had to resort to this and it took hours or days. Actually, months. There
can also be PC-specific or Windows-specific problems, which may or may not be
due to Access, so it's always worth trying another independent machine.
Chris
"Mark in Miami" <mhirt@nhac.org> wrote in message
news:2dbf101c46b75$f8d6aa20$a601280a@phx.gbl...
> I have both Access 97 and 2K running on my machine. I
> can 'open with...' and open my database using Access '97
> no prob. That's where it was created by someone else
> long ago. When I try to open the same database using
> Access 2K, I get the following err:
>
> 'The Visual Basic for Applications project in this
> database is corrupt.'
>
> I looked up this error online and was referred to open a
> blank new project and import the differnet objects,
> tables, queries, macros, reports, forms, modules,
> macros... I did all that there's some mysterious code in
> the background that's keeping macros and other stuff from
> firing right because I get a yes/no notification asking
> that I want to stop the current code execution... bla bla
> bla....
>
> this is not being very friendly.
>
> Can anyone assist?
>
> Mark
- Next message: Sarah M: "Re: Database Front / Back end"
- Previous message: Chris Mills: "Re: Covert an application in Access 2000 to Access 2003"
- In reply to: Mark in Miami: "App running Access '97 vs. Access 2K"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
