VB Forum / Database Access / May 2005

I have inherited an old VB project.
I can open it in VB6, but I get this error when I try to compile or run.
Any help in tracking this down would be greatly appreciated.

I want make a database connection to an Oracle db (8i) with Visual
Basic 2005 express BETA 2.
I already installed Oracle Data Provider for .NET
(http://www.oracle.com/technology/tech/windows/odpnet/index.html)

I have an mdb file that I'm accessing from a vb6 app utilizing dsn-less
connections. This file is local to my application however it is on a
webserver in a Frontpage web site also being accessed by remote users. I
don't have it running up to speed yet and I'm starting to wonder ...

I am trying to exprot recordsets from multiple tables to the same text
file and I don't know all the table names at design time because the
user will be making new ones.
Here's what I have so far.

I'm still stuck on this conversion. Has anyone been successful in
porting an Access 97 database to 2003 using ADO and Jet4?
I've used the sample code on the MS site using "engine type=5" and
Access 2003 still wants to re-convert it when it sees the converted DB.

I there any waty you can provide (and save) a passsword for an ODBC
connection?
My customer has a lot of different products using the same ODBC connection.
It would be really handy if the could supply the password only one place...

Hello --
After following William Vaughn's (6th ed) "Simple DOW Example" to build a
single Record user control (diverging from his Data Grid example on page
896) I get the message

1) How do I catch the Exception thrown from an sqlopen in Excel/VB?
2) It seems that no matter the username or password or DSN is incorrect, the
samme runtime error (13) is thrown. Isn't possible the distinguish between
the different error-situation?

Wonder if you could help me with the problem I've caused myself!!
I have 2 problems both exactly the same and I can't fathom how to get round
them.
PROBLEM 1 (I am using an Access 2000 DB):

After reading a number of old posts about how to correctly package and
distribute a Visual Basic 6 project that utilizes an Access 97
database, I am still having problems. I updated MDAC_TYP.exe in
Wizards\PDWizard\Redist to version 2.8. When I package the application

I have a vb6 application which creates a report on an Access 2003
database.  The ado object connection string currently indicates that
the data base is stored at c:\.  I would like to make this dynamic so
that if, for example, I am running the program in c:\myprogramarea

I am trying to get started with linking VB6 to a simple MDB file.  The
property dialog for the DATA GRID has a data source of DATA Environment.  I
would like to point it to a MDB file called test.mdb.
If I place a DATA control on a form which is linked to a ACCESS 2000 or

I have bound a control to a dataset (it's a drop down box) and have
selected the proper table in the datasource property. I have also selected
the
field for the DisplayMember but the only thing showing in the drop-down box

I'm using vb .net 2003 and MS SQL server DE. I'm using the ADO .net SQL data
controls (SQLConnect, SQLDataAdapter and a dataset). I'm able to retrieve
data from SQL server and populate a form to some databound text boxes.
However, when I make changes to the text boxes and try to ...

I created an app that pulls data from a sql server 2000 machine. If this
program is open for a while and not active on a xp machine and then it tries
to pull new data it can't connect. Below is one of the data access portion of
the app. Have to restart the machine for it to work