mdb too slow for vb. cannot refresh screen.

I fill the Janus Gridex Component with a table. (don't worry problem is not
related with component. I tried listbox also). Then I add a record with
rst.addnew/rst.update methods.

When I call .rebind method to refresh grid, nothing happens. if I refresh it
after 2 seconds, it works. if I put a messagebox that says "new record
added" and gain time, it also works.

But if I refresh grid immediatelly after rst.addnew/rst.update methods, old
recordset comes to screen. same problem also exists in rst.update and
rst.delete methods.

Strange thing is this problem doesn't exists in SQL server. in all form, I
use one adodb.connection and also I tried cn.begintrans / cn.committrans and
wait until cn.state <> adexecuting. it didn't work.

and help please ? thanks.

Aykut,
It is a kludge, but a delay tactic like the one you are using is the only
way to get around the slowness of the MDB platform that I know of. As the
MDB gets bigger, the delay will become longer, so I have resorted to closing
and requerying after adding a record(s) when using MDB database
applications.
CF

"Aykut Canturk" wrote in message

 >I fill the Janus Gridex Component with a table. (don't worry problem is not
 >related with component. I tried listbox also). Then I add a record with
 >rst.addnew/rst.update methods.
 >
 > When I call .rebind method to refresh grid, nothing happens. if I refresh
 > it after 2 seconds, it works. if I put a messagebox that says "new record
 > added" and gain time, it also works.
 >
 > But if I refresh grid immediatelly after rst.addnew/rst.update methods,
 > old recordset comes to screen. same problem also exists in rst.update and
 > rst.delete methods.
 >
 > Strange thing is this problem doesn't exists in SQL server. in all form, I
 > use one adodb.connection and also I tried cn.begintrans / cn.committrans
 > and wait until cn.state <> adexecuting. it didn't work.
 >
 > and help please ? thanks.
 >