What is the best way to export any of the following:

1. Whole Schema, or
2. All Tables with Row Header information, or
3 Individual tables with Header row information


I opened up access and exported all of my tables into csv files, but
it did not include the column name information.
I am trying to export the 1st row, so that I can import into another
type of database that would recognize the 1st row as the field name
row.

Thanks

On Jun 9, 11:34*am, BookerT <ch... (AT) mierbo (DOT) com> wrote:
It depends.

What do you really need to accomplish?

One solution might be to look at the all_tab_columns view. Another
way might be to hard code the column names into another csv file and
concatenate them. You don't do the access equivalent of "select *
from table" do you?

The best way for you might not be the best way for anyone else. Also,
"export" in the Oracle world generally refers to specific tools that
don't do what you want.

There are tools for making csv files, as well as techniques that avoid
using access. There is probably some way to do what you want with VB
or some other MS-thingie, so you can do it directly with access, but I
wouldn't know about that. You might google for it, though. I wrote
some program in an obscure tool that used COM to do magic nice things
directly into ridiculously complicated spreadsheets, then the tool
stopped officially supporting it. It was a real PITA, anyways, and
I'm not looking forward to rewriting all that stuff when the tool
actually stops supporting it.

Maybe cdo.tools or an access group might answer better.

jg
--
@home.com is bogus.
Duuuuuhhhhhh... http://news.cnet.com/8301-13505_3-9962935-16.html

On Jun 9, 11:34*am, BookerT <ch... (AT) mierbo (DOT) com> wrote:
It depends.

What do you really need to accomplish?

One solution might be to look at the all_tab_columns view. Another
way might be to hard code the column names into another csv file and
concatenate them. You don't do the access equivalent of "select *
from table" do you?

The best way for you might not be the best way for anyone else. Also,
"export" in the Oracle world generally refers to specific tools that
don't do what you want.

There are tools for making csv files, as well as techniques that avoid
using access. There is probably some way to do what you want with VB
or some other MS-thingie, so you can do it directly with access, but I
wouldn't know about that. You might google for it, though. I wrote
some program in an obscure tool that used COM to do magic nice things
directly into ridiculously complicated spreadsheets, then the tool
stopped officially supporting it. It was a real PITA, anyways, and
I'm not looking forward to rewriting all that stuff when the tool
actually stops supporting it.

Maybe cdo.tools or an access group might answer better.

jg
--
@home.com is bogus.
Duuuuuhhhhhh... http://news.cnet.com/8301-13505_3-9962935-16.html

On Jun 9, 11:34*am, BookerT <ch... (AT) mierbo (DOT) com> wrote:
It depends.

What do you really need to accomplish?

One solution might be to look at the all_tab_columns view. Another
way might be to hard code the column names into another csv file and
concatenate them. You don't do the access equivalent of "select *
from table" do you?

The best way for you might not be the best way for anyone else. Also,
"export" in the Oracle world generally refers to specific tools that
don't do what you want.

There are tools for making csv files, as well as techniques that avoid
using access. There is probably some way to do what you want with VB
or some other MS-thingie, so you can do it directly with access, but I
wouldn't know about that. You might google for it, though. I wrote
some program in an obscure tool that used COM to do magic nice things
directly into ridiculously complicated spreadsheets, then the tool
stopped officially supporting it. It was a real PITA, anyways, and
I'm not looking forward to rewriting all that stuff when the tool
actually stops supporting it.

Maybe cdo.tools or an access group might answer better.

jg
--
@home.com is bogus.
Duuuuuhhhhhh... http://news.cnet.com/8301-13505_3-9962935-16.html

On Jun 9, 11:34*am, BookerT <ch... (AT) mierbo (DOT) com> wrote:
It depends.

What do you really need to accomplish?

One solution might be to look at the all_tab_columns view. Another
way might be to hard code the column names into another csv file and
concatenate them. You don't do the access equivalent of "select *
from table" do you?

The best way for you might not be the best way for anyone else. Also,
"export" in the Oracle world generally refers to specific tools that
don't do what you want.

There are tools for making csv files, as well as techniques that avoid
using access. There is probably some way to do what you want with VB
or some other MS-thingie, so you can do it directly with access, but I
wouldn't know about that. You might google for it, though. I wrote
some program in an obscure tool that used COM to do magic nice things
directly into ridiculously complicated spreadsheets, then the tool
stopped officially supporting it. It was a real PITA, anyways, and
I'm not looking forward to rewriting all that stuff when the tool
actually stops supporting it.

Maybe cdo.tools or an access group might answer better.

jg
--
@home.com is bogus.
Duuuuuhhhhhh... http://news.cnet.com/8301-13505_3-9962935-16.html

I am just changing from one database to another (A CRM solution)

And in our fact finding, we wanted to test the import function into
the new CRM. The import tool can take as input files, sv files, and
it will use the first row as the header information to create the
equivalent columns in the destination table.

So instead of copying and pasting by hand, I figured there was a way t
oexport table information to include the column names.

On Jun 9, 2:34 pm, BookerT <ch... (AT) mierbo (DOT) com> wrote:

I am just changing from one database to another (A CRM solution)

And in our fact finding, we wanted to test the import function into
the new CRM. The import tool can take as input files, sv files, and
it will use the first row as the header information to create the
equivalent columns in the destination table.

So instead of copying and pasting by hand, I figured there was a way t
oexport table information to include the column names.

On Jun 9, 2:34 pm, BookerT <ch... (AT) mierbo (DOT) com> wrote:

I am just changing from one database to another (A CRM solution)

And in our fact finding, we wanted to test the import function into
the new CRM. The import tool can take as input files, sv files, and
it will use the first row as the header information to create the
equivalent columns in the destination table.

So instead of copying and pasting by hand, I figured there was a way t
oexport table information to include the column names.

On Jun 9, 2:34 pm, BookerT <ch... (AT) mierbo (DOT) com> wrote:

I am just changing from one database to another (A CRM solution)

And in our fact finding, we wanted to test the import function into
the new CRM. The import tool can take as input files, sv files, and
it will use the first row as the header information to create the
equivalent columns in the destination table.

So instead of copying and pasting by hand, I figured there was a way t
oexport table information to include the column names.

On Jun 9, 2:34 pm, BookerT <ch... (AT) mierbo (DOT) com> wrote:

BookerT (chipw (AT) mierbo (DOT) com) wrote:
: I am just changing from one database to another (A CRM solution)

: And in our fact finding, we wanted to test the import function into
: the new CRM. The import tool can take as input files, sv files, and
: it will use the first row as the header information to create the
: equivalent columns in the destination table.

: So instead of copying and pasting by hand, I figured there was a way t
: oexport table information to include the column names.

: On Jun 9, 2:34 pm, BookerT <ch... (AT) mierbo (DOT) com> wrote:
: > What is the best way to export any of the following:
: >
: > 1. Whole Schema, or
: > 2. All Tables with Row Header information, or
: > 3 Individual tables with Header row information
: >
: > I opened up access and exported all of my tables into csv files, but
: > it did not include the column name information.
: > I am trying to export the 1st row, so that I can import into another
: > type of database that would recognize the 1st row as the field name
: > row.
: >
: > Thanks

Are you really sure there is no way in access to "export" the data with
the column names included? I haven't used access for quite some time, but
I thought it had that sort of capability if you choose the right options.

I often plsqldeveloper. In that tool it is easy to query the table,
select all the rows by clicking on the top-left cell, then right click to
get all sorts of copy/save/export options. The CSV option saves the data
including the column names.

I assume that most such tools have that sort of option if you look in the
right place in the tool.

$0.10