Having coded for both in production environments, I strongly suggest that you use the completely unbound version.
Yes it requires a bit more coding on your part upfront but you have much better control of what gets into and does not get into the "database" (your recordset in this case). This allows you to verify data and screen it prior to letting it get into the database. This saves a lot of time in your production environment later for I have found you always acquire erroneous data that just "mysteriously" (I didn't do it... no body did it... it just happened) appears and that you spend numerous hours (due to the problem constantly repeating itself) cleaning out the database of this bad data. Good Luck ____________________________________________________________________________________ Cheap talk? Check out Yahoo! Messenger's low PC-to-Phone call rates. http://voice.yahoo.com
