Access 97 using me! reference

[CQ]

I have lots of references within Access 97 that use
the "me!" method to reference forms, queries and
reports. The database has moved on the network and now
everybody has to map a network drive because we are
getting an error message that it isn't on "L:\\etc\etc".
Well, the person that developed it had it on their
drive "L" but nobody else does.

 

[Dirk Goldgar]

I have lots of references within Access 97 that use
the "me!" method to reference forms, queries and
reports. The database has moved on the network and now
everybody has to map a network drive because we are
getting an error message that it isn't on "L:\\etc\etc".
Well, the person that developed it had it on their
drive "L" but nobody else does.

I don't see the connection between the "Me" keyword and any specific
drive letter. Is the database split into front-end and back-end
databases, with the back-end supposedly on the L: drive? Or are there
other hard-coded references to drive L:?

When the error message appears, does it provide and option to Debug the
code so you can see exactly where the reference to the L: drive is
occurring? If not, can you open a code module and search all modules
for "L:"? Such hard-coded drive letters, and similarly hard-coded
database paths, can be replaced by more flexible code.

 

[Van T. Dinh]

Me is just the short reference to the current data object,
i.e. the current Form or Report.

If you have a split database (Front-End & Back-End), the
fix can be as simple as using the Link Table Manager in
the Menu Tools / Database Utilities... to re-link the
(linked) Tables pointing to the correct network full
pathname of the Back-End. Unfortunately, it can also be
very complex if the original developer hard-coded the path
in the database.

HTH
Van T. Dinh
MVP (Access)