C
Chris Cairns
Before I converted from MDB to ADP I was able to import data from Excel and
..CSV files directly into Access Tables. Microsoft did not include the
ability to save the import specs when using an ADP or ADE. I discovered
that somebody wrote a module that would allow us to reference an .mde file
and use the import specs saved in that .mde file. It worked great. The
file was called TsiImpExp.mde.
My problem. I am running the access app on Access 2003 which requires that
the code be signed or the user has to accept each time it is opened. I
don't have any problem signing my own app, but because the other .mde file
is unsigned and referenced it displays a message each time the app is
opened.
It has been long enough and I don't recall who created the TsiImpExp.mde
file but do they have a signed update available or would they be willing to
release the .mdb so I can sign? I think they were a former microsoft
employee. It is certainly too bad microsoft didn't include his utility in
Access so everyone could benefit from importing using import specs.
..CSV files directly into Access Tables. Microsoft did not include the
ability to save the import specs when using an ADP or ADE. I discovered
that somebody wrote a module that would allow us to reference an .mde file
and use the import specs saved in that .mde file. It worked great. The
file was called TsiImpExp.mde.
My problem. I am running the access app on Access 2003 which requires that
the code be signed or the user has to accept each time it is opened. I
don't have any problem signing my own app, but because the other .mde file
is unsigned and referenced it displays a message each time the app is
opened.
It has been long enough and I don't recall who created the TsiImpExp.mde
file but do they have a signed update available or would they be willing to
release the .mdb so I can sign? I think they were a former microsoft
employee. It is certainly too bad microsoft didn't include his utility in
Access so everyone could benefit from importing using import specs.