Removing warning about unable to save data

[Stephen J. Levine MD]

I think we have probably reached a point of maximum
benefit from our discussion of the merits of distributed
mde front ends and their maintenance vs a centralized
copy. As far as I am concerned, the fact that I can set
my mde fe to read only and have it still function normally
looks very promising in that one should not be able to
corrupt a read-only file. If I pursue this, which I may
have to, the next step would be to stress test the read-
only fe in a heavy multiuser environment to see how robust
it is and whether it is corrupted.

So my last question (and then I'll leave everyone alone)
is to ask if anyone knows of a way to suppress the initial
warning window that the database is locked to edits.

This warning would be irrelevant, since the software is
only manipulating data in the back end database, and would
be potentially a tremendous source of confusion.

Appreciative
sjl

 

[Douglas J. Steele]

You're correct that the warning is irrelevant, but as far as I'm aware,
there's no easy way to avoid it.

I read once that you can open the database through automation from some
other code (a VB program, another Access application or something like
that), but I was never able to get that to work to my satisfaction.

 

[Stephen J. Levine MD]

Doug

That's okay. I have learned on this Newsgroup that, by
including version validation of the front end against the
back end, one can ensure that outdated fe copies do not
work. Thus I am now comfortable with fe's being
distributed to individual pcs where fe corruption risk is
minimized.

I will, however, include setting the fe to read only in
some of my validation test cases to verify that no
writing to the fe occurs. In this situation, the warning
would be part of the expected behavior.

sjl