Just wondering if this is a Windows 7 thing, or a SQL 2008R2 thing, or an issue with my computer, . or something else?
I'm trying to import data from a VFP database to a table in SQL2008R2. Everything is on my local Windows 7 based computer. I start the wizard in SMS and select "Microsoft OLE DB Provider for Visual FoxPro" as the data source, but I get no criteria below to enter information into. When I click on properties I get a message box that says "Unexpected Unrecoverable Error". Gee, that's an informative message. Clicking any of the buttons (Abort, Retry, Ignore) closes the wizard.
Running it on my 64-bit Windows 7 notebook with the 64-bit of Sqlserver just brings up the "Stopped Working" dialog instead. Clicking on "Check for a solution online", as usual, does nothing.
I have uninstalled/reinstalled the VFPOleDB driver to no avail.
Any clues? I could write a VFP program to update the table in SQL, however my directive is to phase out VFP and do as much coding in SQL Server as possible.
TIA,
Lou
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/004601cc73cb$f21c7b90$d65572b0$@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.
You definitely need the 32 bit ODBC administrator to make sure that it's installed properly.
You did see the recent post that MS is deprecating OLEDB, right?
I'll see if I can try this out on my W7 dev system and let you know what happens. How are you attempting to import the data? In SSMS? TSQL script?
--
rk
-----Original Message-----
From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com] On Behalf Of Lou Syracuse
Sent: Thursday, September 15, 2011 1:22 PM
To: profoxtech@leafe.com
Subject: VFPOLEDB issues in SQL 2008R2 / Windows 7
Just wondering if this is a Windows 7 thing, or a SQL 2008R2 thing, or an issue with my computer, . or something else?
I'm trying to import data from a VFP database to a table in SQL2008R2. Everything is on my local Windows 7 based computer. I start the wizard in SMS and select "Microsoft OLE DB Provider for Visual FoxPro" as the data source, but I get no criteria below to enter information into. When I click on properties I get a message box that says "Unexpected Unrecoverable Error". Gee, that's an informative message. Clicking any of the buttons (Abort, Retry, Ignore) closes the wizard.
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/DF1EEF11E586A64FB54A97F22A8BD04419F2CA4F51@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.
Using SSMS, simple as can be for now. Eventually I would build an SSIS job to do it, but if I can't SQL to read the data in SSMS then I don't know how SSIS will read it...
Thanks for checking it out for me!
Lou
-----Original Message-----
From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com] On Behalf Of Richard Kaye
Sent: Thursday, September 15, 2011 10:29 AM
To: profoxtech@leafe.com
Subject: RE: VFPOLEDB issues in SQL 2008R2 / Windows 7
You definitely need the 32 bit ODBC administrator to make sure that it's installed properly.
You did see the recent post that MS is deprecating OLEDB, right?
I'll see if I can try this out on my W7 dev system and let you know what happens. How are you attempting to import the data? In SSMS? TSQL script?
--
rk
-----Original Message-----
From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com] On Behalf Of Lou Syracuse
Sent: Thursday, September 15, 2011 1:22 PM
To: profoxtech@leafe.com
Subject: VFPOLEDB issues in SQL 2008R2 / Windows 7
Just wondering if this is a Windows 7 thing, or a SQL 2008R2 thing, or an issue with my computer, . or something else?
I'm trying to import data from a VFP database to a table in SQL2008R2. Everything is on my local Windows 7 based computer. I start the wizard in SMS and select "Microsoft OLE DB Provider for Visual FoxPro" as the data source, but I get no criteria below to enter information into. When I click on properties I get a message box that says "Unexpected Unrecoverable Error". Gee, that's an informative message. Clicking any of the buttons (Abort, Retry, Ignore) closes the wizard.
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/005101cc73ce$d66b8690$834293b0$@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 Thu, Sep 15, 2011 at 1:21 PM, Lou Syracuse <lous@iconmediadirect.com> wrote:
> Just wondering if this is a Windows 7 thing, or a SQL 2008R2 thing, or an issue with my computer, . or something else?
I had a lot of problems with simple imports (even CSV!) with SSMS on
Win7Pro and it appears it was a problem with my choices during
installation: some of the import/export bits aren't installed by
default with a minimal installation. When I went back to the setup and
added "more stuff" (sorry - months ago, I can't recall exactly what),
it started working better.
--
Ted Roche
Ted Roche & Associates, LLC
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CACW6n4sJzcn8NL3LQgDdeMga_=D=hm41FeBwVDJ7rBLBPMjyVw@mail.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.
Author: Jarvis, Matthew
Posted: 2011-09-15 14:22:50 Link
> I had a lot of problems with simple imports (even CSV!) with SSMS on
> Win7Pro and it appears it was a problem with my choices during
> installation: some of the import/export bits aren't installed by
> default with a minimal installation. When I went back to the setup and
> added "more stuff" (sorry - months ago, I can't recall exactly what),
> it started working better.
I ran into the same thing (though someone else had done the installation
and older OS)... banged my head for hours and hours until I realized it
wasn't ME, it was the package as installed... argh!!!!
On the bright side, my workaround was learning how to use osql and the
LogParser program... ;)
Thanks,
Matthew Jarvis || Business Systems Analyst
IT Department
McKenzie-Willamette Medical Center
1460 G Street, Springfield, OR 97477 || Ph: 541-744-6092 || Fax:
541-744-6145
--------------------------------------------------------------------------
Disclaimer: This electronic message may contain information that is
Proprietary, Confidential, or legally privileged or protected. It
is intended only for the use of the individual(s) and entity named
in the message. If you are not an intended recipient of this
message, please notify the sender immediately and delete the
material from your computer. Do not deliver, distribute or copy
this message and do not disclose its contents or take any action in
reliance on the information it contains.
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/69F310C05DD83C48A84BA3769CE1ECF805A05466@TNTRIEXEVS02.triadhospitals.net
** 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.
Hmm. I just installed Client Tools, but it didn't change anything - still no go.
I have installed everything except Replication, Full-text search and Client Tools SDK; can't imagine they'd have anything to do with it. I can import text, csv, and Excel, the only problem I have found so far is with VFP tables - and of course those are the ones I need.
I wrote a quick VFP program to update the data so I can continue working on the main project.
We are taking small steps towards getting all our apps to SQ,L which we have only had a few months. These little problems will then go away (to be replaced with newer problems, most likely. Lol)
Lou
-----Original Message-----
From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com] On Behalf Of Ted Roche
Sent: Thursday, September 15, 2011 10:50 AM
To: profoxtech@leafe.com
Subject: Re: VFPOLEDB issues in SQL 2008R2 / Windows 7
On Thu, Sep 15, 2011 at 1:21 PM, Lou Syracuse <lous@iconmediadirect.com> wrote:
> Just wondering if this is a Windows 7 thing, or a SQL 2008R2 thing, or an issue with my computer, . or something else?
I had a lot of problems with simple imports (even CSV!) with SSMS on
Win7Pro and it appears it was a problem with my choices during
installation: some of the import/export bits aren't installed by
default with a minimal installation. When I went back to the setup and
added "more stuff" (sorry - months ago, I can't recall exactly what),
it started working better.
--
Ted Roche
Ted Roche & Associates, LLC
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/003c01cc73df$02c18540$08448fc0$@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 Thu, Sep 15, 2011 at 3:38 PM, Lou Syracuse <lous@iconmediadirect.com> wrote:
> We are taking small steps towards getting all our apps to SQ,L which we have only had a few months. These little problems will then go away (to be replaced with newer problems, most likely. Lol)
Oh, yeah.
I think you have the experience to present a good argument to
management that migrating Fox data to SQL Server will be much more
efficiently done using VFP than the SQL Server import tools. I've done
this a few times, and using VFP to take the existing data, rearrange
or clean it to SQL standards, then pushing it to a SQL Server can be a
very efficient process.
--
Ted Roche
Ted Roche & Associates, LLC
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CACW6n4vFgRn_rFK52P86cH456isgAHM_Eoxns78vHbyf9WDQHg@mail.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.
Author: Rafael Copquin
Posted: 2011-09-19 10:18:30 Link
I never liked wizards, to begin with, because one looses control over
how things are done, or what was in the mind of the VFP programmer when
he/she developed the wizard. An example of that is the very intricated
code you find inside your DBC when you want to apply RI to your tables.
I never understood how it worked, and in addition, all error messages
are in English, which is not a language most of my local clients are
proficient with.
Having said that, I always tried to develop my own "wizards" to do
things. And in the case of upgrading to sql server I simply developed my
own two forms. One creates de SQL Server database, tables, constraints
and indexes, fom the VFP DBC, and the other one rearranges VFP data to
SQL Server standards and passes the information from the DBF to the SQL
tables. Works very efficiently, using cursors adapters, and I do not
need the VFP Ole provider at all.
So Microsoft can deprecate it freely, I can't care less.
Rafael Copquin
El 15/09/2011 18:45, Ted Roche escribió:
> On Thu, Sep 15, 2011 at 3:38 PM, Lou Syracuse<lous@iconmediadirect.com> wrote:
>
>> We are taking small steps towards getting all our apps to SQ,L which we have only had a few months. These little problems will then go away (to be replaced with newer problems, most likely. Lol)
> Oh, yeah.
>
> I think you have the experience to present a good argument to
> management that migrating Fox data to SQL Server will be much more
> efficiently done using VFP than the SQL Server import tools. I've done
> this a few times, and using VFP to take the existing data, rearrange
> or clean it to SQL standards, then pushing it to a SQL Server can be a
> very efficient process.
>
>
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/4E774F36.3030803@fibertel.com.ar
** 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.