Darn - I hit a wrong key and sent the e-mail incomplete.

Error was:

- Executing (Error)

Messages

Error 0xc002f210: Preparation SQL Task 1: Executing the query "CREATE

TABLE [dbo].[arch_head] (

[file_type] char..." failed with the following error: "The size

(2147483647) given to the column 'packslip_message' exceeds the maximum

allowed for any data type (8000).". Possible failure reasons: Problems

with the query, "ResultSet" property not set correctly, parameters not

set correctly, or connection not established correctly.

(SQL Server Import and Export Wizard)

Dave - I'm going to take your suggestion and use TEXT field - since that

one will probably NOT give me this problem! Also, although I do like

eating Curry (even though these days I can't do it any longer - as its

even more painful on the Way Out) - I'm generally not referred to as

Kury!

:-)

Kurt

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

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

On Behalf Of Kurt Wendt

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

Seems I didn't scroll down far enough - since the last one I reported

was a Warning - while the following is an actual ERROR - which stopped

the process:

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

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

On Behalf Of Kurt Wendt

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

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

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

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...

_______________________________________________

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/289EA162F5642645B5CF64D624C66A140E260328@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.