User-Specific WorkTables: How to handle MakeTable queries?
- From: "PeteCresswell" <PeteCress@xxxxxxxxx>
- Date: 19 Apr 2006 07:46:21 -0700
When writing to a work DB under C:\Documents and
Settings\[UserName]...., what is the best way to handle MakeTable
queries?
The only approaches I can think of are:
-------------------------------------------------------------------
1) Don't use them. Create a work table in the right DB and replace
the MakeTable query with an goes through a link to the created
table.
2) Every time the app opens, iterate through all the queries, try to
parse out the "IN" statement in each Append query and modify
it accordingly.
3) As above, but update some sort of property that determines the
target DB. But, after a short tour of query properties, I don't
see anything promising.
4) Stop using QueryDefs for MakeTable queries and concoct
inline SQL to do the same job.
----------------------------------------------------------------------
Seems like #2 is just a bug waiting to happen - some unforseen syntax
would blow it up.
There's also the issue of bloating the DB every time the QueryDef is
updated.
RE/#4, I'm not currently into inline SQL for documentation readability
reasons and, probably, pure habit. OTOH, it's not a religious issue
with me.... I *could* mend my ways...
If #3 really is not doable, it seems like #1 or #4 is the way to go.
Anybody else been here?
.
- Follow-Ups:
- Re: User-Specific WorkTables: How to handle MakeTable queries?
- From: (PeteCresswell)
- Re: User-Specific WorkTables: How to handle MakeTable queries?
- Prev by Date: updating a database with more than one version out there
- Next by Date: Boolean criteria with DLookup
- Previous by thread: updating a database with more than one version out there
- Next by thread: Re: User-Specific WorkTables: How to handle MakeTable queries?
- Index(es):
Relevant Pages
|
