Very Computer

1. Converting VFP memo fields to SQL Server text fields

Our VFP application makes rather liberal use of memo fields. For example,
we have an objects table with 25 memo fields in it. We're now attempting
to upsize this application to SQL Server. I see that there are two
datatypes for handling character strings in SQL Server that might be
useful:

1. varchar -- for text strings up to 255 characters

2. text -- for handling variable length text strings; a mimimum of 2K is
allocated for each string

It would appear that the text datatype is the best for our application
because the length of the text strings entered is highly variable. But the
prospect of having records that are a minimum of 50K (25 fields * 2K)
looks like real bad news.

I've been thinking about creating a single text field and placing all the
character string contents in it. In other words, I'd concatenate all the
memo fields' contents together and place them after an index/jump table of
some sort. Before I go to this extreme, though, I was wondering if anyone
here had any other better ideas. Is there some sort of technique that I'm
overlooking?

Geoff LeBlond
Re:discovery Software

2. Let's hope this doesn't become a trend...

3. Copying Memo Fields withing SQL Server

4. Null values or NOT

5. memo field in sql-server

6. How to get a previous row in one result

7. memo fields in SQL server 6.2

8. foxpro efecto 2000

9. Memo field in SQL Server

10. Memo fields and SQL server

11. Memo fields is SQL Server

12. Having trouble with saving Access Memo field in SQL Server

13. Importing Access memo fields to SQL Server 2000