SQL Server Text Fields are good for this. We have a system where the latest EXE versions are stored in a SQL Server Text Field and are then copied to the client and saved as a file.
Remember, a RV is an implementation of SPT. If you can do it in a RV, you can do it in SPT. The converse however is not true. Just because you can do it in SPT, it does not neccessarily mean you can do it in a RV...
>Hi John,
>
>I'm curious... Have you handled image type fields? For example, storing a file in a field, then later extracting that field back to a file on a client's computer.
>
>VFP maps image fields to General data type, but in order to write back the field to a file, the only way I found was using COPY MEMO field TO filename, but in order to use that, the field must be mapped as memo. Using RV, it's a breeze, but I have not found how to do such a thing using SPT.
>
>Any hint?
>
>Thanks!
>
>
>>Remote Views, at best, is an incomplete wrapper around SPT. RV's require you to ceded to much control. Further, if you are going to employ best practices with respect to SQL Server Development, you will use Stored Procedures to Update, Insert, Delete, and Query Data. Stored Procedures provide the level of security and control that developers and DBA's need.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only