Setting Updatable Property of QueryDef to False

[lgs]

In an application, I'm creating a QueryDef on the fly, then use
DoCmd.OpenQuery to display the results.

If the user changes column width, for example, s/he is prompted when
closing whether s/he wants to save the query. This doesn't work
anyway, since it's just a temporary QueryDef, but I'd like to avoid the
whole Save/Yes/No/Cancel dialog box entirely - it's just an annoying
nuisance that could confuse some.

The Updatable property of a QueryDef would seem to be a logical
candidate, but apparently you can only read this property, not set it,
and the default for this property is True, i.e., the QueryDef can be
changed.

Can anyone suggest either a way to set the Updatable property to False,
or in the alternative, intercept this dialog box and bypass it
entirely?

Thanks!

Larry Schmidt

[Salad]

lgs wrote:

In an application, I'm creating a QueryDef on the fly, then use
DoCmd.OpenQuery to display the results.

If the user changes column width, for example, s/he is prompted when
closing whether s/he wants to save the query. This doesn't work
anyway, since it's just a temporary QueryDef, but I'd like to avoid the
whole Save/Yes/No/Cancel dialog box entirely - it's just an annoying
nuisance that could confuse some.

The Updatable property of a QueryDef would seem to be a logical
candidate, but apparently you can only read this property, not set it,
and the default for this property is True, i.e., the QueryDef can be
changed.

Can anyone suggest either a way to set the Updatable property to False,
or in the alternative, intercept this dialog box and bypass it
entirely?

Thanks!

Larry Schmidt

The only way I see you can do this is to pass create a form and set the
form's view as datasheet.

I created a form in the past that allows up to 20 fields. The 20 fields
are unbound. I pass an argument to the form based on what I want
displayed in the form. This determines the SQL for the form's
rowsource. It updates the labels (headings) based on the number of
fields. It turns all fields visible=false that exceed the number of
cols in the SQL. It sets the control source for the fields. It works
fine. It's a bit of work since you have to roll your own, but if you
have 20 or 30 queries you want to pass to it, it's worth it.