One user gets "not a valid path"...

[Guest]

Hi

I have an Access app in production, which is uaed by about 10 different
people. Now a newcomer tried to use the app (which is stored on a shared
drive), but when the first form, triggered by a simple button click, does a
DoCmd to open the next form, she gets a "not a valid path" error !?

She is the only one having that problem, and I have no idea what it can be
due to. All users are using Access 2000, the app is also at the 2000 format,
but I developed most of it with Access 2003.

Any idea what can be done to get rid of that error ? Thanks for help.

Regards
Balex

 

[Jeff Boyce]

Balex

You didn't say if the front-end and the back-end were both stored on the
shared drive, or if only the back-end is stored there. (If the former, you
need to redesign your app to put a copy on each user's PC).

If the latter, perhaps the new user doesn't have the necessary "share" set
up on her PC?

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Jeff Boyce]

That is to say, a copy of the front-end on each user's PC.

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[Guest]

Jeff,

Both f/e and b/e are stored on the same shared drive. All users just click
on the f/e mdb and they have no problems at all using my app

The new user CAN start the front-end without any problems, and selects an
entry in the first form appearing, which causes that form to execute a DoCmd
to open another form in the front-end. However, at this point she gets this
"not a valid path" error, whereas both forms are in the front-end ! OK, that
second form reads from linked tables which are in the back-end, but why
should that not work for her, wheras it works for everybody else, and she
started the f/e from that same locaton where the b/e is ???

Balex

 

[Douglas J. Steele]

How are the tables linked? Using a drive letter (f:\folder\file.mdb), or a
UNC (\\server\share\folder\file.mdb)?

If they're linked using a drive letter, it could be that her drives aren't
mapped the same way.

 

[dbahooker]

****ing dipshits using MDB

Access Data Projects; we dont have maintenance issues like this.

MDB is for retards and babies.
lose the training wheels

-Aaron

 

[Jeff Boyce]

Balex

As a general convention, you'll find that the consensus in these newsgroups
is that you DON'T want a single front-end, shared on a server. This adds
considerably to the network traffic, and I'm surprised the network police
haven't descended on you!

The approach more often recommended is a single back-end on the server, and
a copy of the front-end on each user's PC.

Regards

Jeff Boyce
Microsoft Office/Access MVP

 

[dbahooker]

dipshit

JEFF

dont you understand that _ALL_ use of MDB is a network-performance
nightmare?

does Jet even RUN reliably across a network?

I say that Jet won't run across a network; it's not fast enough; it's
not stable enough


-Aaron
ADP Nationalist

 

[Guest]

Hi Doug,

Yes, the tables are linked via a drive letter. First I thought: "can't be
the problem, this is a big bank, everybody is set up the same way". But...
the IT guys messed it up ! The shared drive for that person has the same name
(drive letter), but it has one level more (at the top) in it, and therefore
is defined differently from all her colleagues ! So the path IS definitively
invalid...

Thanks for putting me on the right path.

Regards

 

[dbahooker]

again; you wouldn't have this kindof maintenance NIGHTMARE if you lost
the training wheels and you used Access Data Projects.

MDB is for retards.
Lose the training wheels.

-Aaron
ADP nationalist

 

[dbahooker]

again; you wouldn't have this kindof maintenance NIGHTMARE if you lost
the training wheels and you used Access Data Projects.

MDB is for retards.
Lose the training wheels.

-Aaron
ADP nationalist