In Access 2K+ the entire VBA access project is saved
as one binary object. You need to have exclusive
control of the object to change it. That means
that you have to have the DB open in exclusive mode
to make design changes.
Is this the problem that you are seeing?
In any case, since you are only talking about
queries, you can use DAO (not ADO) to create new
queries if you have problems using Access methods
(ADO creates queries in a different format, not
the same as Access/DAO queries)
(david)
"CEF" <(E-Mail Removed)> wrote in message
news:066b01c35ae9$654f1ff0$(E-Mail Removed)...
> Nope,
>
> Only Admins has such rights. I even tried giving one of
> the other User Groups the same permissions as Admins, but
> the same "Save Action Canceled" message was still
> produced when executing a Docmd.Save for new queries.
>
> If the SaveAs option from the File menu seems to be the
> only save action that works here, is there some way to
> force saving as a query or a way to prevent/cancel the
> form and report wizards from executing form this dialog
> box??
>
> CEF
> >-----Original Message-----
> >> Why can't a User Group other than Admins save a new
> query
> >> object from a standard module??
> >
> >could be a permissions problem: do other groups
> >have 'open exclusive' permission?
> >
> >(david)
> >
> >"CEF" <(E-Mail Removed)> wrote in message
> >news:796701c35a13$196f2a20$(E-Mail Removed)...
> >> Hi there,
> >>
> >> If someone has a suggestion for my problem, it would be
> >> greatly appreciated.
> >>
> >> I have a secured Access MDE that allows Users to create
> >> and save their own queries. All Users are in Groups
> other
> >> than Admins and permissions set. In Access 97 all
> worked
> >> well. In Access 2K, all works well until the User tries
> >> to save a new query.
> >>
> >> Users create queries using the Access query grid. Their
> >> actions are controlled via options located on a custom
> >> menu. Saves for new queries are only executed when in
> >> design view, two options are being tested:
> >>
> >> 1) File, SaveAs (from Access SaveAs dialog box);
> >> 2) Custom Menu Save Procedure (executes code in a
> standard
> >> module).
> >>
> >> Option 1 allows the User to save the query, but also
> >> gives then the option of saving as form or report, as
> >> well. Not good...I want to force the saves as query
> >> only. The MDE prevents the form or report from being
> >> saved, but, the form and report wizard still executes.
> >>
> >> Option 2 executes DoCmd.Save from a module, but,
> produces
> >> the error "2501 Save Action Canceled". This error only
> >> occurs for Groups other than Admins.
> >>
> >> Is there anyway that the SaveAs Dialog box can be
> >> manipulated so that only the query option is available??
> >> Why can't a User Group other than Admins save a new
> query
> >> object from a standard module??
> >>
> >> I hope I'm just overlooking something. Any
> suggestions???
> >>
> >> Thanks for the assist.
> >>
> >> CEF
> >>
> >>
> >
> >
> >.
> >
|
Similar Threads
