R
Ray
Hi,
We have a bunch of access adps used as front ends for SQL server databases
and recently converted to Access 2007. The problem is that Access 2007
apparently wants to modify the adp which is causing two issues.
First, because the adp is opened for writing, attempting to open a second
instance forces the second instance to be opened in "read only" mode which
displays a save as dialog to save a copy of the adp under a different name.
Because it's connected to an SQL server for data storage, there is nothing in
the adp that should be changed...so opening in read only mode would be fine
if not for the warning message and "save as" option. In fact...opening in
read only mode would fix the secon issue...
The second issue is that we use a "loader app" which examines the date/time
stamp of the adp to determine if it's the latest version. Since the file is
always opened for reading...the file date/time stamp gets updated every time
the adp is opened. That is interfering with our ability to determine if
there is a newer version available.
So...what I'm looking for is a means to suppress the read only warning. I
can understand displaying a warning if it's opening the file as read only
because of a file lock. But if I'm opening the file read only by using the
"/ro" command line switch, do I really need a warning? It seems silly to
warn me about something that I'm obviously doing deliberately. And it's down
right aggravating when there is no way to override that warning.
We have a bunch of access adps used as front ends for SQL server databases
and recently converted to Access 2007. The problem is that Access 2007
apparently wants to modify the adp which is causing two issues.
First, because the adp is opened for writing, attempting to open a second
instance forces the second instance to be opened in "read only" mode which
displays a save as dialog to save a copy of the adp under a different name.
Because it's connected to an SQL server for data storage, there is nothing in
the adp that should be changed...so opening in read only mode would be fine
if not for the warning message and "save as" option. In fact...opening in
read only mode would fix the secon issue...
The second issue is that we use a "loader app" which examines the date/time
stamp of the adp to determine if it's the latest version. Since the file is
always opened for reading...the file date/time stamp gets updated every time
the adp is opened. That is interfering with our ability to determine if
there is a newer version available.
So...what I'm looking for is a means to suppress the read only warning. I
can understand displaying a warning if it's opening the file as read only
because of a file lock. But if I'm opening the file read only by using the
"/ro" command line switch, do I really need a warning? It seems silly to
warn me about something that I'm obviously doing deliberately. And it's down
right aggravating when there is no way to override that warning.