Network access

[Geoff Turnbull]

I have an Access VBA app on a network folder that I'd like to run
simultaneously by multiple users. I can run one instance over the
network, but not two at once, unless the second instance is from the
folder in which the app resides. The second instance doesn't even get
to the security warning. I can run one instance from any computer on
the network--so it seems not to be a matter of permissions, and can run
multiple instances of a C++ app (which opens the Access .mdb file that
hosts the VBA app).
All computers on the network are Vista Home Premium. I am told this
works as desired on another, all-XP, network.
I'd appreciate any ideas on this problem. If there's a better forum,
please advise.
Thanks, Geoff.

 

[Tom van Stiphout]

On Tue, 02 Dec 2008 14:14:52 -0800, Geoff Turnbull

You are violating an important deployment rule.
Access apps should be split in front-end (everything but tables, and
attached tables) and back-end (tables). The BE should be on a server,
the FE on every workstation. Violate this rule and tar & feathers lie
in your immediate future

-Tom.
Microsoft Access MVP

 

[David H]

" I can run one instance over the
network, but not two at once, unless the second instance is from the
folder in which the app resides. "

1) What do you mean by that? Regardless of were the front end is located, if
you open it and it starts and then you open THE SAME FILE you should get two
instances. Period, that's just life.

"All computers on the network are Vista Home Premium"
2) No comment.

"I am told this works as desired on another, all-XP, network. "
3) Yes it most likely CORRECTLY runs on WindowsXP.

If you deploy the Front Ends out as Tom mentioned not only will you be
consistent with an Access best-practice, but you'll be able to get over this
hurdle.

In short, the problem is most likely VISTA.

Now do those ProjectMohave commercials make sense. The vast majority of
corporate America has refused to implement Vista for a wide variety of issues
summed up in one word - VISTA, which in some languages (or so I'm told)
roughly translates to "I suck."
http://weblog.infoworld.com/save-xp/

 

[NTC]

that is snide and poor logic overall....

think about it - 2 people in the same database user space simultaneously;
it should not be possible - - that it is possible with XP and prior versions
is the flaw....and has always lead to unpredictable behavior....

 

[David H]

It is very well known fact that the same Access .mdb file can be opened
multiple times by the same user or by multiple users. I'm merely stating life
as it is.

 

[NTC]

no, you are fundamentally wrong as a point of fact; multi user has always
required multi Front Ends; one per person. that multiusers using a single
Front End would work (sometimes) is not uncommon but can not be exagerated to
the level of belief that it was ever the correct or intended
design/implementation. Thus the fact that it is less viable with a newer
version can not be twisted into a criticism that the newer version is less
good. There is no brand database where 2 different users in the same user
space is intended or guaranteed to work.

 

[Geoff Turnbull]

Quite right: when I separate FE and BE--BE on the network, two
instances will run simultaneously. Don't know why the two Vista and XP
differ in this regard, but they do.
Thanks. And thanks for the discussion of "intended
design/implementation"--it will help guide me in other efforts along
this line.

 

[David H]

Pardon me but if you had read my last post you would have seen that I made no
comment regarding the ABILITY to open the same .mdb file by multiple users or
the same user multiple times. As I stated before, I was merely stating a
fact. No commentary was provided.

no, you are fundamentally wrong as a point of fact; multi user has always
required multi Front Ends; one per person.

NO, you are wrong. The same Access .mdb or .mde file can be opened multiple
times by multiple users simultaneously. It can also be opened by the same
user. (Start Access.EXE and the use the OPEN command)

A .adp or .ade file might be another story.

that multiusers using a single

Front End would work (sometimes) is not uncommon but can not be exagerated to
the level of belief that it was ever the correct or intended
design/implementation.

Please cite explicity where in my last post I stated that it was 'correct'
or allowed intentionally.

Thus the fact that it is less viable with a newer

version can not be twisted into a criticism that the newer version is less
good.

My PC's will NEVER run VISTA as such I will not have the opportunity to
determine whether or not its possible using VISTA. In terms of hard and fast
facts concerning VISTA, consider the fact that corporate America has NOT
implemented it.

There is no brand database where 2 different users in the same user

 

[David H]

(Now back to the regularly scheduled programming...)

Apart from the best practice of having a local copy of the front end on each
PC, Try running the ACCESS.EXE file and then use OPEN.