how to export odbc information from access 2010

Anonymous
2012-02-17T17:33:20+00:00

Is there a way to export linked information in access 2010.  For instance the odbc, server& database names associated with each table?  I found the documenter but that is only for one table and is a mess in excel.

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2012-02-20T05:56:32+00:00

Please post the SQL view of the recordsource of the form and the rowsources of the four combo boxes.

The relationship DOESN'T ACTUALLY MATTER at this point. You do need the relationships, but they won't affect how the form works!

My idea was that you would have tblTablenames with fields (I don't remember and can't scroll back to see them) for AccessDatabaseID, ODBCID, SQLDatabaseID and ServerID, as the Recordsource for your form; the form would not have ANY other tables involved at all. It would have a textbox for the table name and four combo boxes, based on the appropriate tables (AccessDatabases, ODBC, SQLDatabases, Servers) and bound to those four ID fields. You would type in the tablename, and then select the appropriate choices from the four combo boxes. Then you'ld move to the next tablename, and so on.

I haven't any trace of a clue what you mean by "it doesn't work... it shows four records at the bottom".

Again: If you're basing the Form on this multitable query, DON'T. That's not how relationships work, that's not how forms work!!!!

Was this answer helpful?

0 comments
Answer accepted by question author
Anonymous
2012-02-20T04:33:26+00:00

Add fields AccessdbID, ODBCID, SQLdbID and ServerID to tblTableName.

You can then use a Form with combo boxes bound to those fields, based on your database, odbc and SQLdb and Server tables.

It's not quite normalized but a) I think it will meet your current needs and it will be quick and b) it can be used to populate normalized tables if you need to move there.

Was this answer helpful?

0 comments

70 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2012-02-19T23:07:34+00:00

    I just watched a video on using a junction table to create many to many is that the way to do this in access 2010?  You seem to know a better way.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-02-19T22:58:18+00:00

    OK First I'm glad you yelled at me.  Made me pause...I understand what you are saying about the links but am unsure how to make them many to many.  I'm completely confused at that point....you know this is alot harder than my boss made it out to be am i correct about that?

    When i add the sqldatabaseid as a foreign key it adds a second table in the relationships called tblsqldb_1   and they are 1-many for it and for the link to tblsqldb

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-02-19T22:40:23+00:00

    Thank YOU... and sorry I felt that I had to "yell" at you to get here.

    There are a couple of problems that I see. For one thing, the foreign key of a relationship must always be in the "many" side table, linked to the primary key of the "one" side table. So since you could have many different ODBC links to a particular SQL database, it's not correct to have the ODBCID2 field in tblSQLDB. If you do that, then you would be able to set up one, and only one, such link. You need many!

    Since - in the real world - one ODBC link must point to one and only one Database, you need to put the database ID in the ODBC table, not the other way around.

    I'm also not sure that it's appropriate to have a one (SQL/Server database) to many (Access database) relationship. It may be appropriate in your shop, if in practice each Access database is linked to only one SQL instance; but the technology allows for the possibility that you could have one Access frontend linked to two or more SQL backends (and of course you already model the fact that each SQL backend could be linked to multiple Access frontends). Similarly, you could have several different ODBC connections in one Access database, as well as several different Access databases for a given ODBC connection. Do you? 

    Don't change the structure unless you need to - no point in spending a lot of time solving a nonexistant problem! - but I did want to bring up the concern.

    Now a bigger issue. You seem to be making a very common mistake, creating a multitable query (tblODBC joined to tblSQLdb) and using that joined query as the Recordsource for a form. You don't need to do this, and it can and will cause trouble.

    Instead, if - as it appears - you have a linear heirarchy, use Forms and Subforms: a Form for the "one" side table of a relationship, with a Subform for the "many". I think you may be able to use a structure like:

    frmSQLDatabases

       <recordsource tblSQLDB>

       <you'ld just have a combo box on this form to select the SQL Server for this database>

    sbfrmODBC

      <a Subform showing all the ODBC connections to the currently selected tblSQLDB record>

    sbfrmAccessDB

      <a sub-subform showing all of the Access databases that use that ODBC connection>

    sbfrmTables

     <a sub-sub-subform showing all of the tables in that Access database>

    You should certainly consider having a Text field in the table of Tables in which you could store the CONNECT string for that table, available from the Tabledef collection's properties in VBA. It contains the information needed to recover the name of the ODBC connection, the server, the parent table (which might be different than the name of the linked table), etc.

    Good luck and keep posting back... and do try to talk openly to your coworkers and boss about realistic understanding on both sides about what is needed, what is practical, and how much time it may take!

    Was this answer helpful?

    0 comments