Ah okay, that clears that up. I thought you could have done it like this.Originally Posted by szlamany
Code:arBytes() = rs(0).GetChunk(rs(0).ActualSize)
Ah okay, that clears that up. I thought you could have done it like this.Originally Posted by szlamany
Code:arBytes() = rs(0).GetChunk(rs(0).ActualSize)
Regards,
™
As a gesture of gratitude please consider rating helpful posts. c",)
FAQ Submissions: ADO Tutorial | Add record to database | Read/write a text file | Read/write to .Ini | Delete a file | Check file existence | One instance of application | Retrieve running processes / Other stuffs: Mouse Hotkey | Compress file using SQL Server! | Global error handler with stack tracing | WPF - Rounded Combobox | WPF - Notify Icon and Balloon | NetVerser - a WPF chatting system
Yes - that would be the size of the "stored image" - but having that extra column that actually "remembers" the original "size of stored image" would allow me to check "stored image" sizes and find corrupt images...
We also store the original filename...
*** Read the sticky in the DB forum about how to get your question answered quickly!! ***
Please remember to rate posts! Rate any post you find helpful - even in old threads! Use the link to the left - "Rate this Post".
Some Informative Links: [ SQL Rules to Live By ] [ Reserved SQL keywords ] [ When to use INDEX HINTS! ] [ Passing Multi-item Parameters to STORED PROCEDURES ]
[ Solution to non-domain Windows Authentication ] [ Crazy things we do to shrink log files ] [ SQL 2005 Features ] [ Loading Pictures from DB ]
MS MVP 2006, 2007, 2008