Export Specification in Access Project

[Todd K.]

I am developing an Access Project and tried to import an "export
specification" from an Access Database with no luck. The checkbox is there
for import/export specs, but it is grayed out. Am I going to have to
re-create because of incompatibility?

 

['69 Camaro]

Hi, Todd.

I am developing an Access Project and tried to import an "export
specification" from an Access Database with no luck. The checkbox is
there
for import/export specs, but it is grayed out.

The export specification is stored in two Jet tables. Your Access project
does not store local Jet tables. Microsoft recommends using MDB files as
front ends to SQL Server, not ADP files, due to some of the limitations of
ADP files.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.

 

[Todd K.]

I'm going to show my ignorance here, but I thought that's what .adp files
were (Access front ends to SQL back ends).

 

['69 Camaro]

Hi, Todd.

I thought that's what .adp files
were (Access front ends to SQL back ends).

They are. However, ADP's contain no local Jet tables, which is what you
need if you want import/export specs stored in the MSysIMEXColumns and
MSysIMEXSpecs system tables in MDB files.

MDB's have the flexibility to store import/export specs and to link to a
heterogeneous assortment of back ends, such as SQL Server, Oracle, MySQL,
DB2, et cetera, and use all of these tables in queries. ADP's can only
connect to SQL Server tables.

HTH.
Gunny

See http://www.QBuilt.com for all your database needs.
See http://www.Access.QBuilt.com for Microsoft Access tips and tutorials.
Blog: http://DataDevilDog.BlogSpot.com
http://www.Access.QBuilt.com/html/expert_contributors2.html for contact
info.