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-19T20:24:27+00:00

    Artistlover, you're posting a whole lot of emotion and very little fact.

    You can see your database. you know the names of the tables, the names of the fields.

    WE CANNOT. We can only see what you post here in text.

    Please post the following information about your five tables:

    Table name

    All relevant fieldnames

    Primary Key for each table

    What you have tried to relate to what

    Sample data for a few significant fields

    The source of your data: are you typing in database names, trying to extract them automatically from some source, ...?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-02-19T20:03:21+00:00

    if you don't mind see my other thread ..i didnn't mean to start two that ended up going down the same path.  But i'm desperate for help.  I'm running out of time .

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-02-19T19:52:05+00:00

    If you would please explain what you're doing, and in what way it won't work, someone might be able to suggest a fix.

    I can visualize (not write it offhand to a message, but I'm sure it can be done) some VBA code which would search through directories on a network (not CDs or DVDs sitting on someone's desk of course) looking for .mdb, .mde, .accdb, .accde files; opening each of them (with security and password protection being a big hassle!!), looping through the Documents collection to find all the tables, and looking at each table's Connection and constructing such a table. It would be a LOT of work because there's so many ways that a database can be set up.

    I wonder if the first step might be to identify the business-critical applications that get used every day and manually work on them (using the Database Documenter perhaps); then the ones used weekly, then end of month, then those databases that only get opened on the 27th of December for that critical end-of-year report. Working with the people who use the databases is going to be just as important as working with the databases themselves.

    And... I know it's heretical and evil to say it... but sometimes an application will break and it really doesn't make any big difference to anyone!

    Was this answer helpful?

    0 comments