Enabling an Access 97 database for use with Access 2003

[Terry Block]

We have an Access 97 database app that we'd like to enable (not convert) for
Access 2003. We still have users running 97 and are not prepared to upgrade
everyone who uses this database to the 2003 version yet. We're getting an
error message when we try to do this which reads as follows:

"There were compilation errors during the conversion or enabling of this
database. The database has not been saved in a compiled state. The
performance of this database will be impaired because Microsoft Access will
need to recompile the database for each session."

The MS Knowledgebase doesn't provide much guidance on this issue.

Because we cannot enable the database for 2003, the 2003 users cannot get
into the database while 97 users are logged into it (this is unacceptable).

Anyone have any suggestions on how to troubleshoot this issue?

Thanks in advance for any help.

Terry Block

[Fletcher Arnold]

Re: Enabling an Access 97 database for use with Access 2003

"Terry Block" <tblock@ncia.ne t> wrote in message
news:JwO0c.14$i E3.11958@monger .newsread.com.. .[color=blue]
> We have an Access 97 database app that we'd like to enable (not convert)[/color]
for[color=blue]
> Access 2003. We still have users running 97 and are not prepared to[/color]
upgrade[color=blue]
> everyone who uses this database to the 2003 version yet. We're getting an
> error message when we try to do this which reads as follows:
>
> "There were compilation errors during the conversion or enabling of this
> database. The database has not been saved in a compiled state. The
> performance of this database will be impaired because Microsoft Access[/color]
will[color=blue]
> need to recompile the database for each session."
>
> The MS Knowledgebase doesn't provide much guidance on this issue.
>
> Because we cannot enable the database for 2003, the 2003 users cannot get
> into the database while 97 users are logged into it (this is[/color]
unacceptable).[color=blue]
>
> Anyone have any suggestions on how to troubleshoot this issue?
>
> Thanks in advance for any help.
>
> Terry Block[/color]


Starting with the A97 version:
Have you split it front end / back end?
Can you get the code to compile in A97?

Both of these things are pretty essential. Multi-user databases should be
split so that each user has their own copy of the database front end with
forms, reports, code etc and a shared back end which contains the data.
You should also make sure that the code compiles - if not, you may have all
sorts of (horrendous) coding errors.

Once you have this sorted, you can provide different front ends to different
users depending on what version of Access they have, but the shared back end
data should be in A97 format.

Fletcher

[Seth Spearman]

Re: Enabling an Access 97 database for use with Access 2003

Also,

Take a look at tools from FMS to help with this kind of thing. They may
even have a white paper.

https://www.fmsinc.com

Seth B Spearman

"Terry Block" <tblock@ncia.ne t> wrote in message
news:JwO0c.14$i E3.11958@monger .newsread.com.. .[color=blue]
> We have an Access 97 database app that we'd like to enable (not convert)[/color]
for[color=blue]
> Access 2003. We still have users running 97 and are not prepared to[/color]
upgrade[color=blue]
> everyone who uses this database to the 2003 version yet. We're getting an
> error message when we try to do this which reads as follows:
>
> "There were compilation errors during the conversion or enabling of this
> database. The database has not been saved in a compiled state. The
> performance of this database will be impaired because Microsoft Access[/color]
will[color=blue]
> need to recompile the database for each session."
>
> The MS Knowledgebase doesn't provide much guidance on this issue.
>
> Because we cannot enable the database for 2003, the 2003 users cannot get
> into the database while 97 users are logged into it (this is[/color]
unacceptable).[color=blue]
>
> Anyone have any suggestions on how to troubleshoot this issue?
>
> Thanks in advance for any help.
>
> Terry Block
>
>[/color]

[Terry Block]

Re: Enabling an Access 97 database for use with Access 2003

Thanks very much. The database does compile in 97, but I hadn't split it, so
I'll do that and develop a new front end for the 2003 users.

Terry

"Fletcher Arnold" <fletch@home.co m> wrote in message
news:c20hfo$s18 $1@hercules.bti nternet.com...[color=blue]
> "Terry Block" <tblock@ncia.ne t> wrote in message
> news:JwO0c.14$i E3.11958@monger .newsread.com.. .[color=green]
> > We have an Access 97 database app that we'd like to enable (not convert)[/color]
> for[color=green]
> > Access 2003. We still have users running 97 and are not prepared to[/color]
> upgrade[color=green]
> > everyone who uses this database to the 2003 version yet. We're getting[/color][/color]
an[color=blue][color=green]
> > error message when we try to do this which reads as follows:
> >
> > "There were compilation errors during the conversion or enabling of this
> > database. The database has not been saved in a compiled state. The
> > performance of this database will be impaired because Microsoft Access[/color]
> will[color=green]
> > need to recompile the database for each session."
> >
> > The MS Knowledgebase doesn't provide much guidance on this issue.
> >
> > Because we cannot enable the database for 2003, the 2003 users cannot[/color][/color]
get[color=blue][color=green]
> > into the database while 97 users are logged into it (this is[/color]
> unacceptable).[color=green]
> >
> > Anyone have any suggestions on how to troubleshoot this issue?
> >
> > Thanks in advance for any help.
> >
> > Terry Block[/color]
>
>
> Starting with the A97 version:
> Have you split it front end / back end?
> Can you get the code to compile in A97?
>
> Both of these things are pretty essential. Multi-user databases should be
> split so that each user has their own copy of the database front end with
> forms, reports, code etc and a shared back end which contains the data.
> You should also make sure that the code compiles - if not, you may have[/color]
all[color=blue]
> sorts of (horrendous) coding errors.
>
> Once you have this sorted, you can provide different front ends to[/color]
different[color=blue]
> users depending on what version of Access they have, but the shared back[/color]
end[color=blue]
> data should be in A97 format.
>
> Fletcher
>
>[/color]