>I have a simple app I have written with VB6 Enterprise that utilizes a data grid and a data environment with ADO 2.5. The app runs on the server and the data resides in the same directory as the executable. I simply create a shortcut to the .exe on a user's desktop to run the app. I set the connection object in the project to point to the .mdb (Access 97) file on the server (I have used both the .mdb name and the full network path to the .mdb file; \\servername\directory\) and the connection tests good on my machine both ways. I am using a command object comprising of a SQL statement and a cursortype of adOpenKeyset. Even if I compile then create a setup package, install and run the executable from my machine instead of on the server, I can still see the data on the server (if that's where I have pointed the connection). All is well so far. Here is the problem: when I install the package on a user's machine, the app runs, but they cannot see any data. I have even tried dispensing with
>the data environment and using an ADO data control, but with the same results. I am using the Jet OLEDB 3.5.1 provider. I am stumped and would appreciate any advice. Thanks in advance!

Try 2 things:
-Set your CursorLocation to adUseClient.
-Change your provider to Jet OLEDB 4.0