"Michael Porter" <[EMAIL PROTECTED]> wrote: >Second, what kind of data are you going to be storing? If you are going to >be working with large datatypes like images or waveforms, you have a much >more fundamental problem--ODBC won't work for even Windows. My personal >opinion is that ODBC's inherent limitations make it unsuitable for any sort >of serious work unless it's your absolute last hope.
I don't agree on this one. There are certainly problems possible with storing bigger than (usually 65k) of data in one single BLOB field but it all depends on the DB and the tools used. The biggest problem on the client side is that some DB don't support BLOB and if they do the format how to do it is not always the same. Also there are certainly ODBC drivers which simply fail above 32k or 65k. And last but not least having an ODBC interface on your client side which can cope with this is also not always standard. We have had applications where waveforms or complete graphic images were stored into an SQL Server database through ODBC and after some tweaking it worked fine including retrieving the data, although using our own LabVIEW ODBC interface may be one of the reasons it did work. The biggest problem is probably that eventhough BLOBs are supported in some databases, relational databases are not very well suited to store BLOBs. It can be done but is certainly not for what they were normally designed. Rolf Kalbermatter CIT Engineering Nederland BV tel: +31 (070) 415 9190 Treubstraat 7H fax: +31 (070) 415 9191 2288 EG Rijswijk http://www.citengineering.com Netherlands mailto:[EMAIL PROTECTED]
