On Thu, 27 May 2004 06:06:55 +1200, Steve Schapel
wrote:


endus wrote:
split it up, but this is happening with some smaller files that aren't
worth the effort

The effort involved with this is very small. It is not a difficult job.
I am frankly as much in the dark as you regarding the specific causes
of the printer setup problem. But if you have multiple users of the
same application, with access to the design facilities, this kind of
thing is possible. Whereas if each user has their own copy of the
frontend application on their local machine, preferably as an MDE
format, I would expect the risks to be eliminated.


Thanks for the suggestion. This sure is a wierd problem. I tend to
doubt that anyone is specifically changing the printer since they
wouldn't even know which to change it to, but you definitely might be
right that their ability to edit the DB is what allows it to get
changed. I will bring this up as a possible resolution.

Since I posted this I found two references online to a similar
problem. No one seemed to have any idea in either of these places
either, other than that it may be related to opening the DB with
different versions of Access which I don't think is the case in my
situation. For posterity, here are the links...


http://www.experts-exchange.com/Data..._20761664.html

http://groups.google.com/groups?hl=e...30%26hl%3 Den


~ endus ~~ at ~ endus ~ dot ~~ com ~

But what the hell. It is a good & healthy thing
to have a fine fat steak & a bottle of good Kentucky
bourbon & order cameras from Hong Kong & generally
feel rich. - Hunter S. Thompson