Import Schema Problem

[Microbus]

Hell out there,

I am using an import schema.ini to automatically define an input file. The
import works fine.

I then have an export specification that outputs this same data in a
different format.

For some reason, if I try to do the export immediately after doing an
import, Access looses the export specification "the specification does not
exist".

So, I exit out of access, re-enter and run the export spec with no problerm.

Any clues out there are appreciated.

Thanks,

 

[Yoon Meng Yang]

Acyaully this problem no very serious,no need so care this
matter.

 

[Microbus]

Thank you Yoon,

But I do need to care. None of the export specifications work. Access has
lost all the specification (the pointers to the specs are lost!)

So anyone else have a clue to help me out here?

Henry Jenkins

 

[Microbus]

I omitted saying that the "Docmd.transfertext " does not recognize the
Export Specifications in the system table "MsysImexSpecs" - even though you
can see them there.

It seems to me that Access has temporarily changed a system flag to only
uses a schema for the current session.

Henry Jenkins

 

[david epsom dot com dot au]

When this happens, what is the value of
Application.dbengine.inipath

(david)

 

[Microbus]

I found the solutions
ssee MS kb articl Id 241477 - the error is documented and described just as
I described. The workaround says to use the dao.execute method to do the
export/import.


Henry Jenkins.

 

[david epsom dot com dot au]

the error is documented and described just as I described.

I don't see anything there about this:

"So, I exit out of access, re-enter and run the export spec with no
problerm."

Which I why I asked about the value of "Application.dbengine.inipath"

If you are interested, what /is/ the value of Application.dbengine.inipath
when this problem occurs?

(david)