G
Gaetano Deluisi
Hi Guys,
When I use OLE automation in dB2K (the heir of Borland dBase for those who
may not know, currently named dBase Plus) to "talk" to MS Excel, I get the
messge "OLE unknown error: 8002:8018".
With other dBase users, I was able to track the root cause down and it
appears to be related to the regional settings of Windows: if you have an
English version of Windows and you set the regioanl settings to any other
language than English (e.g. French), you are very likely to get this error
while using OLE under dBase. I say very likely, because at least one person
affected by the problem reports that after a clean Windows/Office/dBase
install, the problem does not appear immediately.
This problem was introduced after the original version of Office 97. It
started as soon as I upgraded to the next Service Pack of Office and is
still applicable under Office XP.
What I would wnat to understand is whether it is dBase that passes
information in a wrong way to the OLE server or whether the OLE server does
not take the regional settings into account as it should.
My first impression is that since it used to work before I upgrade Office97,
it should be something on the Office side of the street.
Any ideas/suggestions ? can anyone test this problem with VB between e.g.
Access and Excel after setting the regional settings to French instead of
English with an English version of Windows & Office ?
Many thanks,
Gaetano.
When I use OLE automation in dB2K (the heir of Borland dBase for those who
may not know, currently named dBase Plus) to "talk" to MS Excel, I get the
messge "OLE unknown error: 8002:8018".
With other dBase users, I was able to track the root cause down and it
appears to be related to the regional settings of Windows: if you have an
English version of Windows and you set the regioanl settings to any other
language than English (e.g. French), you are very likely to get this error
while using OLE under dBase. I say very likely, because at least one person
affected by the problem reports that after a clean Windows/Office/dBase
install, the problem does not appear immediately.
This problem was introduced after the original version of Office 97. It
started as soon as I upgraded to the next Service Pack of Office and is
still applicable under Office XP.
What I would wnat to understand is whether it is dBase that passes
information in a wrong way to the OLE server or whether the OLE server does
not take the regional settings into account as it should.
My first impression is that since it used to work before I upgrade Office97,
it should be something on the Office side of the street.
Any ideas/suggestions ? can anyone test this problem with VB between e.g.
Access and Excel after setting the regional settings to French instead of
English with an English version of Windows & Office ?
Many thanks,
Gaetano.