 |
|
Current group: dbase.dde-ole-dll-winapi
OLE Error: 8002:8018, again - in 2.5
| Peter Krarup | | Pier Alberto GUIDOTTI | | Peter Krarup |
|
|
| | From: | Peter Krarup | | Subject: | OLE Error: 8002:8018, again - in 2.5 | | Date: | Wed, 05 Jan 2005 07:33:38 -0500 |
|
|
 | I have just downloaded the trial version to see if the OLe error is still there - when the regional settings is not 'English', and it is!
A simple test is exporting from dQuery to Excel - using the wizard.
Then the error is in line 1703 of qWizExport.wfo.
I wonder if the dBase developers have ever tried to chance the regional settings - to see if they also get the error. The atititude is that it is not a dBase problem, but it would be fine to hear their experience, now they say in the help for dQuery release 2.5:
The Excel export has been rewritten and improved.
If they are able to trace the problem and give an advice how to get around this, it would be a great help. I will not tell all my customers to change their regional settings.
Happy new year.
Peter Krarup
|
|
| | From: | Pier Alberto GUIDOTTI | | Subject: | Re: OLE Error: 8002:8018, again - in 2.5 | | Date: | Fri, 7 Jan 2005 09:50:14 +0100 |
|
|
|
"Peter Krarup" ha scritto nel messaggio
news:ZbUXILy8EHA.1936@news-server...
> I have just downloaded the trial version to see if the OLe error is still
there - when the regional settings is not 'English', and it is!
> A simple test is exporting from dQuery to Excel - using the wizard.
> Then the error is in line 1703 of qWizExport.wfo.
> I wonder if the dBase developers have ever tried to chance the regional
settings - to see if they also get the error. The atititude is that it is
not a dBase problem, but it would be fine to hear their experience, now they
say in the help for dQuery release 2.5:
> The Excel export has been rewritten and improved.
> If they are able to trace the problem and give an advice how to get around
this, it would be a great help. I will not tell all my customers to change
their regional settings.
> Happy new year.
> Peter Krarup
Peter,
The OLE error with Excel occurs only with English versions of Windows when
the "Regional Settings" is different from English. In that situation, Excel
doesn't well recognize Visual Basic method and properties names. This is
definitely not a dBASE problem: if you search for the internet about that
kind of problem, You'll see that many developers, including VB ones,
experienced that error, and that Microsoft said nothing about a possibile
workaround.
Pier Alberto GUIDOTTI
|
|
| | From: | Peter Krarup | | Subject: | Re: OLE Error: 8002:8018, again - in 2.5 | | Date: | Mon, 10 Jan 2005 16:57:33 +0100 |
|
|
| Hello Pier,
Thank you for your answer.
Yes, I have also contacted Microsoft many times about the problem, and have
not got any answer.
The funny thing is that I have other programs, which call Excel
successfully - also with non-english settings, so I wonder how they get
around the problem.
Kind regards
Peter
"Pier Alberto GUIDOTTI" wrote in
message news:6bK5DbJ9EHA.1088@news-server...
>
> "Peter Krarup" ha scritto nel messaggio
> news:ZbUXILy8EHA.1936@news-server...
> > I have just downloaded the trial version to see if the OLe error is
still
> there - when the regional settings is not 'English', and it is!
> > A simple test is exporting from dQuery to Excel - using the wizard.
> > Then the error is in line 1703 of qWizExport.wfo.
> > I wonder if the dBase developers have ever tried to chance the regional
> settings - to see if they also get the error. The atititude is that it is
> not a dBase problem, but it would be fine to hear their experience, now
they
> say in the help for dQuery release 2.5:
> > The Excel export has been rewritten and improved.
> > If they are able to trace the problem and give an advice how to get
around
> this, it would be a great help. I will not tell all my customers to change
> their regional settings.
> > Happy new year.
> > Peter Krarup
>
> Peter,
> The OLE error with Excel occurs only with English versions of Windows when
> the "Regional Settings" is different from English. In that situation,
Excel
> doesn't well recognize Visual Basic method and properties names. This is
> definitely not a dBASE problem: if you search for the internet about that
> kind of problem, You'll see that many developers, including VB ones,
> experienced that error, and that Microsoft said nothing about a possibile
> workaround.
>
> Pier Alberto GUIDOTTI
>
>
|
|
|
| | |
|
 |