If you're concerned about this, what I would do is create each user's DBC with the remote view on-the-fly. You may want to use an identifier you're already keeping as a session variable for the name of the DBC. Then, delete the DBC when you're done. Keep these DBCs in a special sub-directory on the server, and have a routine that deletes any that are left hanging around. (To catch those situations where the user left your site before your app hit the clean-up code.)

>See faq #7995 How to work with Image field type on SQL Server (binary data)?
>
>Sergey,
>
>Interesting article -- I think I will use a remote view!! The only drawback on using a remote view is that it is a web application and I have read that sharing a remote view can lead to some contention issues (in all my desktop apps, the users get there own copy of the remote view DBC).
>
>There will only be 2 to 4 COM servers (using webConnection), so I don't know if the contention issue is serious or not for this scenario.
>
>Thanks for the speedy reply.
>
>Kevin