pietlinden@hotmail.com wrote:[color=blue][color=green]
> > The problem here is that I'm seeing the old query getting deleted and a
> > new one made each time this would run. I'm thinking that could be a
> > problem in a multi user environment if two users clicked the 'Find'
> > button at the same time. I.E., the queryDef is made by User1, but
> > before the SQL statement executes to reference that new query, User2
> > has already deleted and replaced the query with their own criteria
> > based off the multiple objects user2 selected in the listbox.
> >
> > Is there a way I can do this all in a single SQL statement? Or are my
> > fears about queryDefs in multi-user environments unfounded?
> >[/color]
> Why would this be a problem at all if you split the FE and BE? Then
> the qdf would be in the copy of the FE on the local machine, so by
> definition, only one user could use that qdf at a time....[/color]
I wish I could split it. But, I'd have to distribute the FE to 500+
people (It has low numbers of concurrent users before any of you freak
out), and any time a change was made I'd then have to figure out an
effective means of redistributing it to all 500 people. Since it's not
a capital project, the IS department wont give me any backup by just
pushing it out to the designated users.
It's basically a research tool that people will be using infrequently
(perhaps two or three times a month for some). They don't use it often,
but when they do it has to work without any hassles. (such as upgrading
their FE to the latest version).
If I could develop something I knew I'd never have to change, then I'd
do it in a heartbeat. However, they are constantly re-organizing
departments and/or workflows, which can require significant changes to
the UI. In short, this is something that I have to constantly maintain,
and that just isn't easy to do in a FE/BE setup.