Well, the fact is that it working on all those other machines points to some kind of compatibility issue for sure, and so you should work through the options to eliminate this as a possibility. It working on the computer where the printer resides locally might seem to point to something, but it could very reasonably be just a coincidence in that it also works on other systems where the printer is remote.
I would look carefully at all the nonworking systems and find any common features on them that are not common with the working machines. It could be as simple as norton being installed on some and McCafee on the others.
I assume you already tried creating a new db and importing your objects into it and try it from there... that would be an easy first try.
Take one of the non-working systems over to the printer (or vice-versa) and set it up as local and deal with that suspicion.
Try re-installing access - no, actually un-install access and then install it.
On the non-working machines try disabling all non-essential software from running at startup, including services, firewalls and anti-virus software (for the purposes of testing). Then make sure that both the OS and Access are FULLY patched. Then try running access in a compatibility mode.
Try a registry cleaner like the one in Norton SystemWorks to resolve registry issues.
Look for adware or spyware, download and run spybot search and destroy, ip hijacking could be occurring might affect remote printing.
Only way to fix this kind of thing is to eliminate all the possible issues, one at a time.
In the end, Format and re-install your OS on one of them, Patch it completely, Install Access, Patch it completely, try it then. Try it in a compatibility mode. Of course thats drastic, but thats why I said "in the end" :)
John
|
