So, what's the deal? I'm using an .adp (please don't ask why or suggest
i use an .mdb - this is a sore subject and i might snap) and i can't
save a schema when exporting a table as fixed width .txt - furthermore,
using the transfertext method without specifying a schema yeilds less
than desirable results: seemingly picking and choosing which fields to
export with no rhyme or reason. does anybody know more about this? does
EVERYBODY know more about this? am i the only one? please help. thanks.
- krep

p.s. i suppose i could just stream the data into a .txt and force the
column widths, but that's a cheesy cludge - THERE'S GOT TO BE A BETTER
WAY!!!!

oh.. schema-- now i know what you are referring to.

you can use a schema.ini file; this is more powerful.

i believe that you can import the schemas from a MDB into an ADP.. but
then you have to refer to them by name; i dont think that there is a
designer, per-se

I would reccomend looking into bulkinsert and DTS; those tools are much
much much more powerful

-Aaron


(E-Mail Removed) wrote:
> So, what's the deal? I'm using an .adp (please don't ask why or suggest
> i use an .mdb - this is a sore subject and i might snap) and i can't
> save a schema when exporting a table as fixed width .txt - furthermore,
> using the transfertext method without specifying a schema yeilds less
> than desirable results: seemingly picking and choosing which fields to
> export with no rhyme or reason. does anybody know more about this? does
> EVERYBODY know more about this? am i the only one? please help. thanks.
> - krep
>
> p.s. i suppose i could just stream the data into a .txt and force the
> column widths, but that's a cheesy cludge - THERE'S GOT TO BE A BETTER
> WAY!!!!