Building A VB program to pull a project into Access.

Please restate your question, explaining more clearly what exactly you are trying to move where.

I am trying to move a project which is a collection of tables and query's in .mdb format with different database relations into access through the use of Visual Basics 2005.  Visual Basic is the vehicle in which the info will transferred.  Maybe let me know what is unclear so I can answer a little more specific.

So you have an Access .mdb file that contains Tables and Queries, and you want to move those Tables and Queries to a NEW Access file ... and you want to do this from VB.NET?

Define "different database relations".

>Define "different database relations".
(Off Topic)  Jeff Foxworthy suddently comes to mind.

jimhorn - lol, Meaning that the tables within the project are connect via different queries and are associated with eachother in more then on relationship.

LSMConsulting - Exsactly!  The Project within this program is storred as a access .mdb file and I would like to use VB.  I was under the impression that I could use VB 2005 and not .NET.  Is this the same thing?  Definition for different Database relations refer to comment made to jimhorn.

<(Off Topic)  Jeff Foxworthy suddently comes to mind. >

LMFAO ... you're a sick one, Jim ...

VB 2005 is, basically, just another name for VB.NET ...

You can use an Access database in VB or .NET ... in either, you would simply build a connection to your database and use the data as needed, whether that be a Table or a Query. You don't need to transfer anything to VB or .NET in order to use the database.

In VB6, you can connect to the db via DAO or ADO.

In .NET, you'd use a DataAdapter, IIRC (haven't worked in .NET for a while).

Hopefully I'm on the right track ...

Ok, I didn't know about that terminology, thanks.  So yes normally you could just send a file containing tables, forms, queries...etc., in Access into another file within Access, but I need to use VB as a vehicle to grab the file within a program (program is built with VB as well I tihnk) and then I will later, after I develop the connection, do some filtering in database to grab certain work groups, areas or components. Work groups, area and components are all set up with the database as paretn child relationships.

But you are on the right track.  So what would be my 'DataAdapter"?  Don't I need a shell or form that mirrors the form of the incoming projects, in access in order to edit them within VB?

Thanks alot!!