Access Run-time Error

[isbjornen]

(I've cross-posted this questions)
-----------------------------------------
Hello,

I've developed an Access 2002 dbase and distributed it as a run-time
application.

Here's the problem:
On 2 user's PC (out of roughly 40 installed) I get the message "You do not
have exclusive access to the database at this time. If you proceed to make
changes, you may not be able to save them later."
I'm NOT trying to open the dbase for design. The start-up command line is
not corrupted either - it starts up as a run-time application. What's
interesting is that I have to close the message box 31 times before it
disappears.
Both PC's do have Access 2000 installed, but I haven't had any problems with
any other user with the same configuration.

Any suggestions/ideas?

Thanx!

 

[Bill Mosca, MS Access MVP]

Does your startup form have any Load or Open event code that might be trying
to make design changes?

 

[isbjornen]

Not really, 'On Load' I resize access to "fit" 800x600 screen resolution,
but it has never caused any problems before (i.e. other dbases I've released)

 

[Bill Mosca, MS Access MVP]

By any chance, are those 2 users just double-clicking the database file to
open it...or using a shortcut with the db file as the target? When using
either of those methods to open a database, Access tries to open it
exclusively.

 

[isbjornen]

Both users (and everybody else) use a shortcut with "/Runtime" in the Target
command line. Never had a problem with it before.

 

[Bill Mosca, MS Access MVP]

Something is not jiving here. If you use the Runtime switch as far as I know
that automatically puts the database in the same mode as if it were an MDE.
I would think you would not be able to open it exclusively as there would be
no point in doing so.

I guess I'm saying I don't have an answer for you, but you might take a look
at the Access application settings on those 2 machines to see if they are
set to open all DBs exclusively (Tools>Options>Advanced tab).

By the bye, if everyone is using the runtime switch , why don't you just
create an MDE fo reach user?

 

[isbjornen]

<snip> "...but you might take a look at the Access application settings on
those 2 machines to see if they are set to open all DBs exclusively
(Tools>Options>Advanced tab)..."</snip>

Already did it.

<snip> "...if everyone is using the runtime switch , why don't you just
create an MDE for each user?...</snip>

Not everybody has Access.

Thanks for trying to help.

 

[Bill Mosca, MS Access MVP]

<<Not everybody has Access.
That doesn't really enter into it or I'm confused as to what you are saying.
If you are using the /Runtime switch, everyone must have Access installed.
But even if some users don't have Access installed and you are using the
runtime files instead, an MDE would still work.

 

[isbjornen]

<snip> "...but you might take a look at the Access application settings on
those 2 machines to see if they are set to open all DBs exclusively
(Tools>Options>Advanced tab)..." </snip>

Already did that - it's set to Shared.

<snip> "...if everyone is using the runtime switch , why don't you just
create an MDE fo reach user?..." </snip>

Not everybody has Access installed.

Thanks for trying!!!

 

[isbjornen]

<snip> "...but you might take a look at the Access application settings on
those 2 machines to see if they are set to open all DBs exclusively
(Tools>Options>Advanced tab)..." </snip>

Already did that - it's set to Shared.

<snip> "...if everyone is using the runtime switch , why don't you just
create an MDE fo reach user?..." </snip>

Not everybody has Access installed.

Thanks for trying!!!

 

[isbjornen]

As far as I know, Access Runtime installs a freely distributable copy that
can run Access programs - no design/edit rights - if the Access program is
made into a Runtime app. I've tried to open a regular MDB program with
Runtime - it didn't work *correctly.* Never tried it with a MDE though - I
guess I could experiment with it...

Thanx again!

 

[Bill Mosca, MS Access MVP]

An MDE should be constructed as if it were running in the runtime
environment. Users should have the same restrictions if the DB is properly
designed. This makes the MDE look and act the same whether the user has
Access or Runtime installed.

It's far too easy for a user to circumvent the Runtime if the y have Access
installed. An MDE gives you much more control.