Problem with Front end / Back End files

  • Thread starter Thread starter Savvoulidis Iordanis
  • Start date Start date
S

Savvoulidis Iordanis

There are many times that the front end doesn't go to look
for the back end file (eg. when I copy it to a another PC).
It just opens, and of course when I try to access anything, I can't.

The way I do it is:
In the AppInit function I try to access a backend table and if I get an
error, then I prompt the user to point to the backend file. But as I said,
sometimes it doesn't happen.

Does it have to do with the Access setup on the client PC or not
and what can I do if it doesn't?

TIA
 
Iordani,

Are you using drive mappings in your links? Any chance it doesn't work on
some PC's because of different / missing drive mapping? If that's the case,
then you don't need to resort to code tricks and require user intervention,
just use UNC addressing instead of the drive mappings, and your problem will
be solved.

HTH,
Nikos

P.S. don't post your e-mail address undistrorted in the newsgroups, you're
in for big time spam!
 
Thanks for the post.

I always use the UNC format. Drive mappings are excluded. But anyway, this
problem appears when working on my own PC (when I change the name of the
server file for testing purposes). I use Access2000 on W2000 Pro SP3 on my
PC.
I can't say I can always reproduce this behavior. Most off the times I get
the fileopen dialog to select the server PC.
But sometimes I don't. The app starts, but of course it crashes when it
tries to access the DB.

Another problem I have is that when I install the same app on the network,
on W98 PC/Access 2000, although the net connections are OK (I can see the
server \\SERVER\c\Pegasus...), when I select the server file and try to
reconnect the client tables, it seems that I can't. Is it possible that
there is a user permissions issue on the server's OS level?

Looking forward to reading an answer...
 
Back
Top