corrupt jet after joining xp pro to new domain

Archived from groups: microsoft.public.windowsxp.help_and_support (More info?)

Very strange thing happened. one of the windows xp pro workstations which
was working perfectly fine, it now exhibiting some very strange behaviour
when trying to register jet 4.0 which we need for a bespoke program to work.

Basically what happened is we put in a new server, and to join the existing
computers to the new domain, we ran the file and settings tranfer wizard on
each machine, disjoined them from the existing domain, rejoined them to the
new domain and ran the file and settings tranfer wizard to import the user
settings etc.

Since then a bespoke program whcih we use on all workstations doesnt work on
this one workstation. I have locked it down to failure to correctly install
jet 4.0 when logged on as any other user apart from the local administrator.
If you log onto the computer as domain admin or as a domain user with local
admin rights it fails to install jet 4.0 and cannot register any of the dll
files, even though they exist in system32.

I am very confused by this and am on the verge of reformatting the computer
to overcome this. I would be very grateful if anybody else has any other
suggestions to resolve. this one.

Andy Heywood