525 Data Access Error - German Version of Windows - ADO DAO RDO RDS

<wjk@corvetsys.com> wrote in message
news:1188819135.325373.73760@k79g2000hse.googlegroups.com...
> It does not solve the problem of why reinstalling the MDAC and Jet4
> engine did not solve the problem if you are correct. The one thing
> that I do know is ..... formatting the system and reinstalling the OS
> cures it every time.
>
> What a horrible user solution for me to recommend.
>

Not necessarily. Consider that if it takes something that drastic to make a
simple app work. They were only headed for trouble down the road with
something else.

Tell them, "We are sure lucky we caught this in time." <g>

-ralph

> Not necessarily. Consider that if it takes something that drastic to make a
> simple app work. They were only headed for trouble down the road with
> something else.
>
> Tell them, "We are sure lucky we caught this in time." <g>


And you can say that with a straight face???? You da' Man

OK.... we have found something... changing the regional language
settings to English has eliminated the 3170 ISAM error and the
software works.

I wonder ... other than switching to a German language based build
computer if I can somehow get it to work.

<wjk@corvetsys.com> wrote in message
news:1188915947.018347.257610@k79g2000hse.googlegroups.com...
> OK.... we have found something... changing the regional language
> settings to English has eliminated the 3170 ISAM error and the
> software works.
>
> I wonder ... other than switching to a German language based build
> computer if I can somehow get it to work.
>

If you can track it down to a specific "language" problem, eg, "periods
instead of commas", date formats ("12/1/07 vs 1/12/07"), then there are some
conversion routines that always read the local settings and others that
always assume "us".
Depending on the specifics there is always a work-around.

-ralph