Re: Output to a text file

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



You can import the import and export specifications from another database
this way:

In the database that is to "get" the specifications, go to File | Get
External Data ... | Import. Select the database that contains the
specifications. In the wizard screen, click the Options button at bottom
right; you'll see a checkbox that is next to "import/export specifications".
Check the checkbox, and then do the import.
--

Ken Snell
<MS ACCESS MVP>



"Alec M1BNK" <AlecM1BNK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4AC24122-F8E5-41A7-B560-E96656FCAFD4@xxxxxxxxxxxxxxxx
Yes, that much I do know, that's how I created the original spec in my dev
copy of the database.

I solved the problem by getting everyone out of the working copy and
redefining the spec there, but is there not a way I could have exported
the
spec from my dev copy to the working copy of the database.

Or indeed, is there a better way for me to export a tab delimited text
file
than the above.

"Ken Snell (MVP)" wrote:

The second argument of the TransferText method is the name of an export
specification that you created and stored in the ACCESS database. This is
done manually by beginning the export process (File | Export), going
through
all the screens to set the field specs, field names, etc., then on the
last
screen of the wizard click the Advanced button at bottom left of the
screen.
There you can save the specifications as an export specification. Then
use
the name under which you store them as the export specification argument
in
your code.

--

Ken Snell
<MS ACCESS MVP>

"Alec M1BNK" <AlecM1BNK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D5A9E58D-693E-4BF0-B243-14D81D413C23@xxxxxxxxxxxxxxxx
Hi all (again)

Once again i find myself having to dip into the pot of
wisdom...............

I have a multi user access databse. it's stored on a network server and
people access it by a mapped network drive.

I have a specific need to output the results of a query as a tab
delimted
text file. So, I defined a spec, in this case called "samfileout" and
added
this code to an on click event

DoCmd.TransferText acExportDelim, "samfileout", "q_SamUpload",
"samupload.txt", False

When I exported this from my dev copy to the working one on the network
it
doesn't work. Users get a runtime error that the filespec "samfileout"
does
not exisit. Where do i find this filespec and how do I export it to
other
users?

I've searched the helpfiles and knowledge base but what help there is
is
on
Import not export, and does not seem applicable in this case.

Alternatively, is there a better way to this, where everything is
contained
inside the database.





.



Relevant Pages

  • Re: Size matters to some
    ... logical and implementation specifications from a developer. ... The underlying remote database connection ... physical layer is actually managing it all, the logical layer is forced to ... predictable amount of hardware resources and CPU time per transaction. ...
    (comp.databases.pick)
  • Re: What is Field F1?
    ... >>>There is no automated /wizard way to transfer import specifications from ... Open the new database and begin the Import process (File ... When the wizard window ...
    (microsoft.public.access.gettingstarted)
  • Re: Help needed on import/export specifications
    ... I have successfully imported the specifications into my newly-created tables ... database cannot update, ... > For schema.ini (which is used instead of import/export specifications), ... >>tables(MSysIMEXSpecs and MSysIMEXColumns) using the schema.ini files. ...
    (microsoft.public.access.externaldata)
  • Re: Copy import specifications
    ... How can one "import" an Import Specificaton File from another database? ... "Joan Wild" wrote: ... >> specifications button. ... >> that the server version has the correct specs. ...
    (microsoft.public.access.externaldata)
  • Re: Help needed on import/export specifications
    ... > and is able to use the specifications but when i try to export using the ... > database cannot update, ... >> For schema.ini (which is used instead of import/export specifications), ... >>>tables(MSysIMEXSpecs and MSysIMEXColumns) using the schema.ini files. ...
    (microsoft.public.access.externaldata)