Package and Deployment

[Devija]

I'm just learning to use VB6. I have built several programs with MS Access. I now have created an application in VB6 using tables from Access 2000. I created a Data Environment and Commands and Child Commands. My controls are bound to those commands. Everything works great on my machine. I run Package and Deployment, it finishes sucessful. I run the package on another machine and it doesn't connect to the data. When the form comes up no data is showing and if you try to navigate an error pops up about the DSN not found and no default driver provided. Obviously, I'm overlooking something very simple here. I thought that Package and Deployment would build all those things into the application from the Data Environment used at design time. Do you have to build the connection strings and commands into the code?? If so what is the purpose of Data Environment?? Anyway, any help would be appreciated.

Thanks

 

[Sheffield]

Does the DSN that your DataEnvironment uses physically exist on the pc that you are installing the program to?

 

[Devija]

Well, the DSN is not on the machine I am installing to. I guess I need to understand the process this thing uses. What I am trying to do is convert some Access applications to VB apps using the data from the original Access program. So I designed the forms and recreated what I had done in Access. I used the Data Environment to create all commands and child commands needed. When I created the connection under Data Environment I used provider Microsoft OLE DB provider for ODBC Drivers, under the connection tab I chose DSN as Microsoft Access Database and the initial catalog pointed to the database that contained my tables. Everything worked great. I created my commands, and can drag them on the form, rearrange everything to look the way I want and run the program. It all works great on the machine I am setting up. I package the application and go to install it on another clean workstation and everything installs fine, no errors. When I run the app, the form comes up fine but there is no data in any of the fields and if you click a navigation button you get the error mentioned before. Somehow, I am overlooking the part that binds the form controls to the data when it is installed on a clean workstation. Thanks for any help you can provide.

 

[Devija]

Well, I figured out how to get what I wanted here. I changed the connection in my Data Environment. Instead of choosing the DSN as Microsoft Access Database, I used the connection string and built a file DSN and everything worked great when I packaged it and deployed it on another machine.

Thanks for the help

 

[OLLYBEAR]

I am new to VB6. I have created a simple application in VB6
that uses tables in ACCESS 2000. When I use Data Environment
to create a form, the contents of the Fields in ACCESS appear.

One of the fields is of type OLE (a bitmap image),called Photo.

When I run the application I am told that vb6 cannot bind to field or dataformat: Photo

However, if I use a data control the image in the field Photo does appear.

Desperate for help

Thanks
OLLY