Bob while I can't answer this particular question I thought I would ask a question of my own that might solve the problem.
Why do you need to bind any fields to the database? I ask this because the real power of ADO is not to have a "permanent" connection to the database. You read the data (snapshot) locked or unlocked, then adjust the data, then write the data. This is the simpliest outline, now if you have issues with heavy amounts of multiple users then there are other disconnected methodolgies that handle this as well. Oh and subsequently it also solves any potential problems from Binding fields. Just food for thought. --- bobisagroupy <[EMAIL PROTECTED]> wrote: > We are trying to redo our database and will use SQL > as a backend with Access as the Frontend. We have > seen there are problems using ADO to edit bound > forms in Access 2000. Has this been fixed in any > of the latest releases or are there any patches to > help with this. > Thanks > Bob > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/AccessVBACentral/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
