I have the fix, but I can't find out how to prevent the problem.

The problem is, that I have some users can run all the macros and then I have some who can not run the macros. The fix is, go to there default printer and change there options, such as print one sided to two sided, then change it back to one sided.

Running 2003 and on a network.

It appears every time our network people do there upgrades, that is when it happens, but not to all users.

Come on some of you gurus help me out on this, please.

You have to post this one in a different group. Try Macro.
You have to give more information; what does it do? Howmany users do you have. Do you have a FE/BE set up?
Level of experience? Can't you use VBA instead?
In short, more info.

Guus2005,
Thanks for the reply. I posted this question in General, due to I think the problem is due to more than just a macro, its a macro that its affecting. If that makes sense. The problem will affect all macros i.e. printing, opening and closing forms.

There can be 10 to 15 users at one time.
Yes I have FE/BE.
Ten years plus in Access.
I suppose I could use VBA, but it just seems faster when I design a Macro in Access.

Remember it only applies to some users not all. I have some users it does not affect at all. For myself it has never happen to me. I don't want to point fingers, but I think it has to do something with the server. If its a database issue, why doesn't it happen to everyone, just a select few? I think they have different servers which the database sits on. Now I am just guessing, I am not a hardware person, nor a great software person.

I think what you're saying is that when the network people install upgrades of some sort, some of your users lose their printer settings while others do not. This is a guess here, but is everyone using different printers? If that's the case, that can be a source of the issue. Are all the users that use one printer being affected, while the users of other printers are not affected?

When you say "the network people do their thing", it sounds like you are in a corporate environment where mass updates are applied to multiple computers at once, and some of these people use one printer or type of printer while others are using a different set, and those updates are "resetting" the printer to defaults. Without going through IT, there's not much you can do but programmatically put the printer information into code and set it each time.

If you're doing reports, this is very easy: Me.Printer.<property>

Scroll through what IntelliSense gives you to see all the properties/attributes you can define.

Moniker, thanks for taking a look at this tread. Now you got me to thinking of another approach.

Yes I am in corporate environment with various printers.

I just don't think I can solve this problem. It would be great when it does happen, some type of code would fire up, not being a code person I don't think its possible.

Or is it?

Appreciate your input or anybody.

Assuming it's reports, I already gave you the answer. Put the code I gave earlier (Me.Printer.<property>) into the report, and you don't have to worry about updates. This goes in the report's On Format or On Open event. I would use On Open for printing.

Moniker, I will give it try and see what happens. Thanks for the input, I will keep my fingers crossed.