Exporting a table...

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am trying to export a table out of access that also includes the
description of the data, and not only the unique ID. When run a query, the
table has the exact information that I want to export. But when I do export
it and then open it in another program, it replaces the text info in the
cells with it's unique ID number, which is not what I want.

Any ideas?
 
I bet that you are using lookup fields or subdatasheets. I HATE those things.
You just found out one reason and there are many more.

Your query will need to contain both the parent table and child table to
extract the data if I am right.
 
Hi Bryan,

It sounds like your table includes Lookup Fields. Table Lookups are
considered evil by many, and you've just discovered one reason why. See the
2nd commandment here for more information:

The Ten Commandments of Access
http://www.mvps.org/access/tencommandments.htm

You'll need to create a query that includes the table that your table lookup
field is currently referencing. This table should be joined to your existing
table with a join line (it will be if you have already implemented
relationships, under Tools > Relationships). Otherwise, you will need to join
the tables to prevent a cartesian product result.


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

I am trying to export a table out of access that also includes the
description of the data, and not only the unique ID. When run a query, the
table has the exact information that I want to export. But when I do export
it and then open it in another program, it replaces the text info in the
cells with it's unique ID number, which is not what I want.

Any ideas?
 
Yes, you were both exactly right. I am just learning so I guess that is part
of it. Thank you very much for your help! I will have to see what I can do...

Regards-
Bryan
 
That brings up another question....

If I would have created these lookup tables by entering data through forms,
would I still have the same problem?
 
Hi Bryan,

If you create a table lookup, and then use the form wizard to create a form
based on that table, you will get a combo box. Combo boxes on forms are fine.
You would likely still get the numeric value stored in the foreign key field
(ie. the control source of the combo box). So I guess the only difference is
that you would have seen immediately that the field in the table contained a
numeric reference, instead of displaying a lookup up value for you.

In general, you want to avoid table lookups. Combo boxes on forms work nicely.


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

That brings up another question....

If I would have created these lookup tables by entering data through forms,
would I still have the same problem?
 
Tom-

Could I send an email to you that explains what I am trying to do? I have
been struggling with this, and I would really appreciate any help.

Thanks
 
You must log in or register to reply here.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Exporting query to table in external database 4
Exporting design view tables 0
Exporting Multiple Tables to Text 2
Exporting / Importing forms and tables 2
problems exporting tables 1
Replacing a Table with a Table from another database - reference issues 1
Exporting a table/Query to a text and Price columns won't align ri 6
Export to Excel 3

Back
Top