By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,310 Members | 1,430 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,310 IT Pros & Developers. It's quick & easy.

ODBC Connector

P: n/a
I am using ODBC 4.51 and mySQL 4.0.1-NT. I have an app that is written in
vb6 with msAccess 2000 that was converted to mySQL. Everything is working
great except for one thing.

I have a grid of information (using TrueGrid v7) and I need the grid to
update with the newest data.

In msAccess (ADO) I used the adUseServer Cursor / Dynamic Recordset and then
all I had to do was do a tdbgrid1.refresh to get the latest data.
Everything was working just as I wanted.

In mySQL(ADO) when I use the adUseServer, I get no data returned to the
grid, and if I debug the data, it is there, but it doesn't refresh (in the
debug window). Changing to adUseClient puts the data in the grid, but
obviously doesn't refresh either.

The grid will have varying number of records depending on the query, but in
general it will have a couple of hundred records (with about 30 showing at
one time). What I need to be able to do, as an example, is to page down so
that records 60-90 are showing and refresh any new data that is coming in
without moving grid. I can do this programmatically, but was wondering if
anyone knew away around this. It worked perfectly with the msAccess engine.

BTW the options I have on the ODBC are 18475
Jul 19 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Sorry ODBC 3.51

"David Codding" <dc******@saicorporate.com> wrote in message
news:10*************@corp.supernews.com...
I am using ODBC 4.51 and mySQL 4.0.1-NT. I have an app that is written in vb6 with msAccess 2000 that was converted to mySQL. Everything is working
great except for one thing.

I have a grid of information (using TrueGrid v7) and I need the grid to
update with the newest data.

In msAccess (ADO) I used the adUseServer Cursor / Dynamic Recordset and then all I had to do was do a tdbgrid1.refresh to get the latest data.
Everything was working just as I wanted.

In mySQL(ADO) when I use the adUseServer, I get no data returned to the
grid, and if I debug the data, it is there, but it doesn't refresh (in the
debug window). Changing to adUseClient puts the data in the grid, but
obviously doesn't refresh either.

The grid will have varying number of records depending on the query, but in general it will have a couple of hundred records (with about 30 showing at one time). What I need to be able to do, as an example, is to page down so that records 60-90 are showing and refresh any new data that is coming in
without moving grid. I can do this programmatically, but was wondering if anyone knew away around this. It worked perfectly with the msAccess engine.
BTW the options I have on the ODBC are 18475

Jul 19 '05 #2

P: n/a
Sorry ODBC 3.51

"David Codding" <dc******@saicorporate.com> wrote in message
news:10*************@corp.supernews.com...
I am using ODBC 4.51 and mySQL 4.0.1-NT. I have an app that is written in vb6 with msAccess 2000 that was converted to mySQL. Everything is working
great except for one thing.

I have a grid of information (using TrueGrid v7) and I need the grid to
update with the newest data.

In msAccess (ADO) I used the adUseServer Cursor / Dynamic Recordset and then all I had to do was do a tdbgrid1.refresh to get the latest data.
Everything was working just as I wanted.

In mySQL(ADO) when I use the adUseServer, I get no data returned to the
grid, and if I debug the data, it is there, but it doesn't refresh (in the
debug window). Changing to adUseClient puts the data in the grid, but
obviously doesn't refresh either.

The grid will have varying number of records depending on the query, but in general it will have a couple of hundred records (with about 30 showing at one time). What I need to be able to do, as an example, is to page down so that records 60-90 are showing and refresh any new data that is coming in
without moving grid. I can do this programmatically, but was wondering if anyone knew away around this. It worked perfectly with the msAccess engine.
BTW the options I have on the ODBC are 18475

Jul 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.