Multiple instances of an adp...

[Ray]

Hi,

With Access 2003, we were able to open multiple instances of an adp on one
machine. Since changing to Access 2007, the first instance opens normally,
but the second and subsequent instances display a "read only" message. Since
we're using adps connecting to an SQL server, there is nothing in the ADP
that should be changing anyway so opening read only all the time would be
fine. The problem is the message. Is there a way to suppress the read only
message. ALternately...is there a way to make multiple instances cooperative
so they don't need to be read only?

Thanks,

Ray

 

[Unknown Name]

WHAT DO U MEAN

 

[Ray]

I mean I would like to be able to have multiple instances of the same access
adp open on the same machine without being warned that the second and
subsequent instances are being opened read only. The users are manipulating
data in a SQL server so I don't care if the adp is opened read only or not.
I'm not concerned about the users changing any forms as I have all of that
locked down. I just don't want my users to have to deal with the warning
message.

It seems dumb to me but another post indicated that it was not possible to
suppress the read only message. I'm wondering if there are any other options.

Ray

 

[Sylvain Lafontaine]

The problem is not about the forms themselves but about the compiled result
required to run a form (form + VBA code behind the form + any called module)
and which must be stored in the ADP project like it is for any MDB or ACCDB
database file.

This compiled state is highly dependant on the version of Windows (OS +
Service Packs) and of Access running on the client's machine and because of
that, it has always been suggested by MS in the past that every client
should run his or her very own copy of the ADP project; in exactly the same
way and with any MDB or ACCDB file.

I don't know about ADP 2007 but personally, I would do the same with this
version.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)

 

[Rayn63]

Hi,

Thanks for the response. But I'm not sure I was clear enough in my
question. We have two basic problems. The archetecture is that each user
has a shortcut to a shared mdb. The mdb simply compares the file date/time
stamp of the copy on the network with a copy in a directory on the users
local drive. If the copy on the network is newer, the older version on the
users local drive is overwritten with the new version from the network. The
mdb then runs the adp from the users local drive and the mdb closes. Access
2007 has created 2 problems.

First, since the date/time stamp of the adp on the users local drive keeps
changing...it sometimes never figures out that a newer version is on the
network. The date/time stamp of the adp did not change under Access 2003.

Second, opening a second instance of an adp from the users local drive
worked just fine under Access 2003. Now, the second copy gives a "read only"
warning which freaks out the users.

I can find another means to deal with the first problem if I have to...but
the ability to open the adp in read only mode without receiving the read only
message would solve both my problems. Is there any way to do that?

Thanks

Ray

 

[Sylvain Lafontaine]

I don't have Access 2007 installed but I did make some checking. First, the
following article clearly state that the first user open the Access project
in exclusive mode - so that he or she can make modifications to the
forms/reports/modules if necessary and that any other second users will open
it in read-only mode:

http://office.microsoft.com/en-us/access/HA010345391033.aspx

You can force the first user to open the project in read-only mode by
setting the read-only protection for the file in Windows Explorer or by
using the /ro startup option (http://support.microsoft.com/kb/209207 ).
However, the first user will also see the warning about the read-only mode -
something that you probably don't want to see but possibly could solve your
problem with the time flag changing.

For the rest, relying on the time flag to compare for a newer version is
probably something risky by itself.

Tony Toews has made public an auto-updater that should work properly even
with an ADP project file if using the option « Use
StartMethod=FileExtension » which is new in version 1.77; see
http://www.autofeupdater.com/ and http://www.autofeupdater.com/faq/index.htm
.. You will also find some other interesting informations about your problem
on this site.

Finally, I don't understand how you managed to open more than one instance
of an adp from the users local drive without seeing the warning message with
Access 2003.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)