I am trying to test an application the imports an Excel spreadsheet on
Windows 8. It won't work because Windows 8 has two ODBC Managers. The
32 bit manager has all of the drivers in it, but Windows 8 will not look
for them. There are no Office 2003 drivers in the 64 bit manager.
Do I need to use a different connection string? Has anyone noticed that
Office 2003 support ends today too?
this has been working for me all along:
lnsqlhandle = SQLSTRINGCONNECT("Driver={Microsoft Excel Driver (*.xls,
*.xlsx, *.xlsm, *.xlsb)}; DBQ=" + lcspreadsheet + ";")
--
Jeff
Jeff Johnson
jeff@san-dc.com
SanDC, Inc.
623-582-0323
Fax 623-869-0675
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/53440AC0.4040201@san-dc.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Silly question but is the 32 bit version of O2003 installed on this system? Assuming there was such a distinction with O2003?
--
rk
-----Original Message-----
From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Jeff Johnson
Sent: Tuesday, April 08, 2014 10:42 AM
To: profoxtech@leafe.com
Subject: [NF] Excel 2003 on Windows 8
I am trying to test an application the imports an Excel spreadsheet on Windows 8. It won't work because Windows 8 has two ODBC Managers. The
32 bit manager has all of the drivers in it, but Windows 8 will not look for them. There are no Office 2003 drivers in the 64 bit manager.
Do I need to use a different connection string? Has anyone noticed that Office 2003 support ends today too?
this has been working for me all along:
lnsqlhandle = SQLSTRINGCONNECT("Driver={Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)}; DBQ=" + lcspreadsheet + ";")
--
Jeff
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/DF1EEF11E586A64FB54A97F22A8BD04422A73C4115@ACKBWDDQH1.artfact.local
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Yes, this is Office 2003 32 bit.
On 4/8/2014 7:55 AM, Richard Kaye wrote:
> Silly question but is the 32 bit version of O2003 installed on this system? Assuming there was such a distinction with O2003?
>
> --
> rk
>
> -----Original Message-----
> From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Jeff Johnson
> Sent: Tuesday, April 08, 2014 10:42 AM
> To: profoxtech@leafe.com
> Subject: [NF] Excel 2003 on Windows 8
>
> I am trying to test an application the imports an Excel spreadsheet on Windows 8. It won't work because Windows 8 has two ODBC Managers. The
> 32 bit manager has all of the drivers in it, but Windows 8 will not look for them. There are no Office 2003 drivers in the 64 bit manager.
>
> Do I need to use a different connection string? Has anyone noticed that Office 2003 support ends today too?
>
> this has been working for me all along:
> lnsqlhandle = SQLSTRINGCONNECT("Driver={Microsoft Excel Driver (*.xls, *.xlsx, *.xlsm, *.xlsb)}; DBQ=" + lcspreadsheet + ";")
>
> --
> Jeff
>
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/53440E12.8000807@san-dc.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
http://support.microsoft.com/kb/2721825/EN-US
does that help?
Al
-----Original Message-----
From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Jeff
Johnson
Sent: 08 April 2014 16:56
To: profoxtech@leafe.com
Subject: Re: [NF] Excel 2003 on Windows 8
Yes, this is Office 2003 32 bit.
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/004a01cf533b$3281d8a0$978589e0$@com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On 04/08/2014 10:42 AM, Jeff Johnson wrote:
> I am trying to test an application the imports an Excel spreadsheet on
> Windows 8.
So, a Visual FoxPro application, right?
> It won't work because Windows 8 has two ODBC Managers.
All 64-bit Windows systems have two ODBC Managers. That's a good thing
(tm). Otherwise, we 32-bit developers would be left out in the cold.
> The 32 bit manager has all of the drivers in it, but Windows 8 will
> not look for them.
I think you misunderstand the situation. VFP, a 32-bit app, will only
work with 32-bit ODBC drivers. If you have them, you're good.
> There are no Office 2003 drivers in the 64 bit manager.
>
> Do I need to use a different connection string? Has anyone noticed
> that Office 2003 support ends today too?
Considering the level of MS support, I hadn't noticed.
>
> this has been working for me all along:
> lnsqlhandle = SQLSTRINGCONNECT("Driver={Microsoft Excel Driver (*.xls,
> *.xlsx, *.xlsm, *.xlsb)}; DBQ=" + lcspreadsheet + ";")
When you say, "all along," you mean on systems other than this one?
Other than Windows 8? Other than Office 2003?
Do you have access to a command window on this machine? if so, you can
figure out the correct SQLStringConnect for this machine.
lnHandle = SQLCONNECT() # follow the prompts to open an excel file.
? SQLGetProp(lnHandle, "ConnectString")
More on this at: http://fox.wikis.com/wc.dll?Wiki~VFPCommandSQLStringConnect
--
Ted Roche & Associates, LLC http://www.tedroche.com/
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/53440F93.9080608@gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Allen: I saw that but did not understand what I am to do.
"To locate the 32-bit Office System drivers, use the appropriate version
of the ODBC Administrator tool. If you build and then run an application
as a 32-bit application on a 64-bit operating system, you must create
the ODBC data source by using the ODBC Administrator tool in
%windir%\SysWOW64\odbcad32.exe. For example, the default location on a
Windows 7 64-bit machine is “C:\Windows\SysWOW64\odbcad32.exe”."
I have no idea what this means. I am a lunkhead.
On 4/8/2014 7:59 AM, Allen wrote:
> http://support.microsoft.com/kb/2721825/EN-US
> does that help?
> Al
>
> -----Original Message-----
> From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Jeff
> Johnson
> Sent: 08 April 2014 16:56
> To: profoxtech@leafe.com
> Subject: Re: [NF] Excel 2003 on Windows 8
>
> Yes, this is Office 2003 32 bit.
> --
> Jeff
>
> Jeff Johnson
> jeff@san-dc.com
> SanDC, Inc.
> 623-582-0323
> Fax 623-869-0675
>
>
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/53440FE7.7080709@san-dc.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On 4/8/2014 8:02 AM, Ted Roche wrote:
> On 04/08/2014 10:42 AM, Jeff Johnson wrote:
>> I am trying to test an application the imports an Excel spreadsheet on
>> Windows 8.
> So, a Visual FoxPro application, right?
Yes
>> It won't work because Windows 8 has two ODBC Managers.
> All 64-bit Windows systems have two ODBC Managers. That's a good thing
> (tm). Otherwise, we 32-bit developers would be left out in the cold.
Is that Trade Mark?
>> The 32 bit manager has all of the drivers in it, but Windows 8 will
>> not look for them.
> I think you misunderstand the situation. VFP, a 32-bit app, will only
> work with 32-bit ODBC drivers. If you have them, you're good.
>
>> There are no Office 2003 drivers in the 64 bit manager.
>>
>> Do I need to use a different connection string? Has anyone noticed
>> that Office 2003 support ends today too?
> Considering the level of MS support, I hadn't noticed.
>
>> this has been working for me all along:
>> lnsqlhandle = SQLSTRINGCONNECT("Driver={Microsoft Excel Driver (*.xls,
>> *.xlsx, *.xlsm, *.xlsb)}; DBQ=" + lcspreadsheet + ";")
> When you say, "all along," you mean on systems other than this one?
> Other than Windows 8? Other than Office 2003?
Yes, other machines. Most of them have later versions of Office, but I
don't use Office and all I have is 2003.
> Do you have access to a command window on this machine? if so, you can
> figure out the correct SQLStringConnect for this machine.
>
> lnHandle = SQLCONNECT() # follow the prompts to open an excel file.
>
> ? SQLGetProp(lnHandle, "ConnectString")
>
> More on this at: http://fox.wikis.com/wc.dll?Wiki~VFPCommandSQLStringConnect
>
Thanks Ted!
--
Jeff
Jeff Johnson
jeff@san-dc.com
SanDC, Inc.
623-582-0323
Fax 623-869-0675
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/53441113.5020400@san-dc.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
If you type ODBC into the W8 search box you should get two matches; One for the 64 bit and one for the 32 bit. You will probably have to hunt down the ODBC drivers if they are not appearing in the 32 bit ODBC Manager. I would expect to find them on the O2003 installation media.
--
rk
-----Original Message-----
From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Jeff Johnson
Sent: Tuesday, April 08, 2014 11:04 AM
To: profoxtech@leafe.com
Subject: Re: [NF] Excel 2003 on Windows 8
Allen: I saw that but did not understand what I am to do.
"To locate the 32-bit Office System drivers, use the appropriate version of the ODBC Administrator tool. If you build and then run an application as a 32-bit application on a 64-bit operating system, you must create the ODBC data source by using the ODBC Administrator tool in %windir%\SysWOW64\odbcad32.exe. For example, the default location on a Windows 7 64-bit machine is "C:\Windows\SysWOW64\odbcad32.exe"."
I have no idea what this means. I am a lunkhead.
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/DF1EEF11E586A64FB54A97F22A8BD04422A73C4138@ACKBWDDQH1.artfact.local
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On 4/8/2014 8:20 AM, Richard Kaye wrote:
> If you type ODBC into the W8 search box you should get two matches; One for the 64 bit and one for the 32 bit. You will probably have to hunt down the ODBC drivers if they are not appearing in the 32 bit ODBC Manager. I would expect to find them on the O2003 installation media.
>
> --
> rk
>
> -----Original Message-----
> From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Jeff Johnson
> Sent: Tuesday, April 08, 2014 11:04 AM
> To: profoxtech@leafe.com
> Subject: Re: [NF] Excel 2003 on Windows 8
>
> Allen: I saw that but did not understand what I am to do.
>
> "To locate the 32-bit Office System drivers, use the appropriate version of the ODBC Administrator tool. If you build and then run an application as a 32-bit application on a 64-bit operating system, you must create the ODBC data source by using the ODBC Administrator tool in %windir%\SysWOW64\odbcad32.exe. For example, the default location on a Windows 7 64-bit machine is "C:\Windows\SysWOW64\odbcad32.exe"."
>
> I have no idea what this means. I am a lunkhead.
Okay, I found VFP ODBC drivers and installed them. Now it works with
the below connection string with one slight problem
lnsqlhandle = SQLSTRINGCONNECT([Provider=Microsoft.ACE.OLEDB.12.0;
Data Source="Excel.dsn"; DBQ=] + lcspreadsheet + [; Extended
Properties="Excel 8.0; HDR=YES";])
The Data Source must be incorrect because a window pops up and says
select data source. I select Excel.dsn and it works.
<rant>I can't believe the amount of time spent getting things to work on
Windows 8 that worked fine on Windows 7! ODBC, Remote Desktop, simple
network connections. Sheesh!</rant>
--
Jeff
Jeff Johnson
jeff@san-dc.com
SanDC, Inc.
623-582-0323
Fax 623-869-0675
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/534425A0.6060705@san-dc.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
It's not the VFP ODBC driver you need installed; it's the Office ODBC driver(s). I don't think that gets installed by default with Office but I could be wrong as I haven't installed Office in quite some time. You have to dive into the advanced installation stuff, iirc.
--
rk
-----Original Message-----
From: ProfoxTech [mailto:profoxtech-bounces@leafe.com] On Behalf Of Jeff Johnson
Sent: Tuesday, April 08, 2014 12:37 PM
To: profoxtech@leafe.com
Subject: Re: [NF] Excel 2003 on Windows 8
Okay, I found VFP ODBC drivers and installed them. Now it works with the below connection string with one slight problem
lnsqlhandle = SQLSTRINGCONNECT([Provider=Microsoft.ACE.OLEDB.12.0;
Data Source="Excel.dsn"; DBQ=] + lcspreadsheet + [; Extended Properties="Excel 8.0; HDR=YES";])
The Data Source must be incorrect because a window pops up and says select data source. I select Excel.dsn and it works.
<rant>I can't believe the amount of time spent getting things to work on Windows 8 that worked fine on Windows 7! ODBC, Remote Desktop, simple network connections. Sheesh!</rant>
--
Jeff
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/DF1EEF11E586A64FB54A97F22A8BD04422A73C41A7@ACKBWDDQH1.artfact.local
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.