RE: Memo Fields in SQL [was...RE: SQL Server Import & VFP Data Source]

Author: Kurt Wendt

Posted: 2012-05-15 at 11:32:49

After sending the last e-mail, I decided to turn to my Russian buddy

here (of the 4 other programmers here - he is the ONLY Nice one!). He

suggested I used NVarchar. Is that not a good option?

And, yes, the fields were just holding regular Text type data before.

Sounds like the Text field is probably the best option to use - as you

suggested.

FYI - after I reset the Mappings for those fields to convert as

NVarchar, it let me proceed with the conversion - but, then it ran into

errors when the conversion was actually in process. One of those errors

are as follows:

Setting Source Connection (Warning)

Messages

Warning 0x80202066: Source - arch_head [1]: Cannot retrieve the column

code page info from the OLE DB provider. If the component supports the

"DefaultCodePage" property, the code page from that property will be

used. Change the value of the property if the current string code page

values are incorrect. If the component does not support the property,

the code page from the component's locale ID will be used.

(SQL Server Import and Export Wizard)

Do I actually need to open up the files in VFP and change some kind of

Code Page???

-K-

-----Original Message-----

From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com]

On Behalf Of Dave Crozier

Sent: Tuesday, May 15, 2012 12:28 PM

To: profoxtech@leafe.com

Subject: RE: Memo Fields in SQL [was...RE: SQL Server Import & VFP Data

Source]

Kury,

If you want to hold Blob data then use Varbinary(Max) but if it is just

text data (memo field) use text.

The ODBC driver maps Memo in VFP directly to Text in SQL and vice versa.

Dave

-----Original Message-----

From: profox-bounces@leafe.com [mailto:profox-bounces@leafe.com] On

Behalf Of Kurt Wendt

Sent: 15 May 2012 17:12

To: profox@leafe.com

Subject: Memo Fields in SQL [was...RE: SQL Server Import & VFP Data

Source]

So, I'm now in the middle of trying to convert the VFP data to SQL - and

I get an error like this:

`po_lines` -> [dbo].[po_lines]:

- The data type could not be assigned to the column

"packslip_line_msg_line_no1" in "SQL Server Native Client 10.0".

- The data type could not be assigned to the column

"vendor_line_notes" in "SQL Server Native Client 10.0".

I know it's the issue w/Memo fields - since SQL doesn't have anything

like it. But, if I want to use something even CLOSE to a memo field

within SQL - what type of field should I use? I saw there is Char,

VarChar, Text and more - I just don't the actually differences between

them.

TIA,

-K-

-----Original Message-----

From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com]

On Behalf Of Kurt Wendt

Sent: Tuesday, May 15, 2012 11:20 AM

OK - my Bad!

Obviously I need to go into that Properties button & select the VFP DBC

- before I can hit Next. I made the wrong assumption before - figuring

that when I hit NEXT - it would THEN prompt me for the VFP DBC that I

wanted to Import.

Once I selected the VFP DBC from within the Properties button - I was

now able to successfully hit the Next button.

Just FYI - I've never really worked with SQL before - at least not the

extent of setting up an SQL Database or even installing SQL.

-K-

-----Original Message-----

From: profoxtech-bounces@leafe.com [mailto:profoxtech-bounces@leafe.com]

On Behalf Of Kurt Wendt

Sent: Tuesday, May 15, 2012 11:11 AM

In regards to my previous discussion on here - I just installed MS SQL

Server 2008 R2 Express. And, upon looking under programs to run it - I

found this "SQL Server Import and Export Wizard" tool. So - I ran it -

and found that one of the Data Sources available to choose from is

"Microsoft OLE DB Provider for Visual FoxPro". However, upon selecting

that option and hitting Next - I get an error window "Feature is Not

Available. (Microsoft OLE DB Provider for Visual FoxPro)

So - does that just mean that it's not available under the Express

version? IF that IS the case - I find it quite annoying, since if the

feature is supposed to be N/A - then it should NOT even allow you to

select it to begin with!!!

Just to add - I saw the Properties button under the Data Source

selection drop-down, but, I did NOT change any of those Properties.

Thanks,

-K-

[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/289EA162F5642645B5CF64D624C66A140E260326@us-ny-mail-002.waitex.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.

©2012 Kurt Wendt