Problem with queries

[Ralph BOSWELL]

Hi,

I'm working with Access 2003 on Access 2000 databases. Everything works
alright and I want to keep the databases in the Access 2000 format as I
have to share these databases with our client,using exclusively Access 2000.

The problem is when I have to transfer only queries to my client. The
way I was doing it when I was using Access 2000 was to create a new
database and import the queries I wanted to this new database.
Everything was fine, our client receiving this database just imported
just these queries in his database and his database was up to date.

My problem is that when I do the same thing in Access 2003 (on Access
2000 databases), Access looses all queries definition as the tables upon
which the queries are defined are intentionally not transferred to the
'transfer database'. This was working just fine in Access 2000.

Can someone tell me what to do to be able to transfer only the queries
objects without having to transfer the underlying tables too.

Thanks in advance,

Ralph

 

[Douglas J. Steele]

Sounds as though your application isn't split into a front-end (containing
the queries, forms, reports, macros and modules), linked to a back-end
(containing the tables and relationships). You should be replacing the
entire front-end each time, not trying to modify objects in it.

However, I haven't seen the behaviour you're describing. Queries objects are
strings of SQL. If there are inaccuracies in the SQL (table names mispelled,
etc.), then yes, the query won't behave properly in the new environment, but
other than that, things should be fine.

 

[Nikos Yannacopoulos]

Ralph,

Another way to do it is this: once you have created a new query, switch
to SQL view, copy the SQL expression and past into a text file (or .rtf,
or .doc, it doesn't matter). Then, send that to your client, who will
need to start creating a new query (design view), add no tables, then
switch to SQL view and paste the SQL expression from the text file, and
save under the same query name. I'm pretty sure there are no differences
in the SQL language between the two Jet versions, so that should work.

HTH,
Nikos