Setting the Properties on a Table that was made by a MakeTable Que

[Guest]

I have some very complex queries written and some end users that don't have
access to the queries and tables. So I am making a Form that will run this
query. The first step is to press a button that runs a MakeTable Query. But
this is a replicated database and when the table is made it is made as a
Local table instead of a Replicable table. I can manually go into change
this- but the people who will be running this report don't have access to
this. Is there a way to get the MakeTable query to automatically set the
table property as replicable?

 

[John W. Vinson]

I have some very complex queries written and some end users that don't have
access to the queries and tables. So I am making a Form that will run this
query. The first step is to press a button that runs a MakeTable Query. But
this is a replicated database and when the table is made it is made as a
Local table instead of a Replicable table. I can manually go into change
this- but the people who will be running this report don't have access to
this. Is there a way to get the MakeTable query to automatically set the
table property as replicable?

I don't think so, at least not at all easily.

Why not instead have a stored table? Rather than running a MakeTable query at
all, empty the table and run an Append query to populate it.

John W. Vinson [MVP]

 

[Guest]

But then each time the query is run-we will have duplicated records posting
to the table each time right? Or does the Append query automatically know
which records would be duplicated and not write those to the table?
Basically the query is currently looking at a Notes or a record file and
picking out all the records that have an Event of Offer Accepted (application
database), and taking the date associated with this "Event" and writing it to
a table to store the Offier Accepted Date-so I can run suc-cycle time to fill
reports.

 

[John Spencer]

I think you missed a step. John specifically said DELETE all the records in
the table and then APPEND the
records. That will have the same effect as doing a make table.

Your description of the purpose of this table does make me suspicious as to
why you even need to create the table. You can normally use a query as if
it were a table. This is good because it will eliminate bloat in your
database - and since you are using replication I would avoid making
unneeded changes to a table.

--
John Spencer
Access MVP 2002-2005, 2007
Center for Health Program Development and Management
University of Maryland Baltimore County
..