>Houston:
>
>--------------------------------------------------------------------------------
>>>Does anyone know what datatype a MS Word 97/2000 document should be saved in SQL Server 7?
>--------------------------------------------------------------------------------
>>If your file is less than 8000 bytes (note this is not 8K, which is 8 * 1024) then you could use varbinary. Anything bigger would have to use image.
>
>FYI: A couple of years ago I tried using SQLEXEC() to store large text strings in a Sybase table and found it would not work. An updateable view however did work. I'm curious (and I'm sure others also) to see which route you go down, so please post a response when you get it to work.
>--------------------------------------------------------------------------------
>
>New Word document are 19K if you are using the Word default settings...
>
>Although I have not not tried saving Word documents in SQL Server, we did encounter several formatting problems when trying to restore a document stored as a General field in a VFP database. Because I had to restore the exact document (including formatting) and because of their size, we ended up saving ZIP version of the document (usually 2-3K) in a Memo field. We used DynaZip for all zipping and unzipping operations.
>
>Daniel

---

Why are you replying to me - your post should have been to the original thread creator!

Anyway.

RE: Initial size of Word Doc file. These days I more or less assume that files will be subject to some sort of compression. So a small Word Doc would (as you indicate) fall under the 8000 byte limit for varbinary fields.

Also - General Field, were these linked or embedded? And if editing was not done in situ would a Memo (binary) field have worked eqally well?