How to prevent losing custom queries during an update.

[robert d via AccessMonster.com]

My main application is split, uses custom menus and does not display the
database window. Some users want to be able to create their own queries.

So I created a separate small app that can be used for queries. It also does
not display the database window, but allows users to create Select queries
only.

What I'm wondering is: if I have to update this small querying app, how will
I keep users from losing the individual queries that they've created once
they upgrade to the new version. The new version, of course, won't have any
of the user's custom queries that they created with the previous release.

Also, I want to exted this querying app to allow users to create reports as
well. So my previous question applies to custom queries and reports - how to
keep them from being lost during an update.

 

[Duane Hookom]

Consider the query by form applet found at
http://www.rogersaccesslibrary.com/OtherLibraries.asp#Hookom,Duane. I put it
in almost all applications I create. Query definitions are actually stored
in a couple tables. These can be loaded and modified. Results are a couple
clicks from sending to Word, Excel, Print, CSV, HTML,....

 

[robert d via AccessMonster.com]

Duane:

What you put together looks interesting and I intend to look at it more
closely. But I'm unclear how this solves my problem. I don't see how any
"reports/queries" created by the user are saved so that they won't be lost if
your app needs to be upgraded.

Thanks.

Consider the query by form applet found at
http://www.rogersaccesslibrary.com/OtherLibraries.asp#Hookom,Duane. I put it
in almost all applications I create. Query definitions are actually stored
in a couple tables. These can be loaded and modified. Results are a couple
clicks from sending to Word, Excel, Print, CSV, HTML,....

My main application is split, uses custom menus and does not display the
database window. Some users want to be able to create their own queries.

[quoted text clipped - 16 lines]

to
keep them from being lost during an update.

 

[Duane Hookom]

The query definitions are stored in tables in your back-end database.
Changing the front-end will have no effect on the previously designed
queries/reports.

--
Duane Hookom
MS Access MVP
--

Duane:

What you put together looks interesting and I intend to look at it more
closely. But I'm unclear how this solves my problem. I don't see how any
"reports/queries" created by the user are saved so that they won't be lost
if
your app needs to be upgraded.

Thanks.

Consider the query by form applet found at
http://www.rogersaccesslibrary.com/OtherLibraries.asp#Hookom,Duane. I put
it
in almost all applications I create. Query definitions are actually stored
in a couple tables. These can be loaded and modified. Results are a couple
clicks from sending to Word, Excel, Print, CSV, HTML,....

My main application is split, uses custom menus and does not display the
database window. Some users want to be able to create their own
queries.

[quoted text clipped - 16 lines]

to
keep them from being lost during an update.

 

[robert d via AccessMonster.com]

Okay:

I guess I didn't pick up on that. So since I might have up to 40 users, I
can just add User ID to the table that stores these query definitions and
that would provide a means for retrieving that user's queries.

That should work. I guess it didn't really occur to me because it's user-
specific and I think of a backend as providing data to all and not
necessarily holding individual user preferences.

Thanks!

The query definitions are stored in tables in your back-end database.
Changing the front-end will have no effect on the previously designed
queries/reports.

Duane:

[quoted text clipped - 19 lines]

 

[Duane Hookom]

You could set a default value in the "Author" field in the QBF "header"
table to store the user ID. Then set the first "quick" menu to display only
their queries.

--
Duane Hookom
MS Access MVP
--

Okay:

I guess I didn't pick up on that. So since I might have up to 40 users, I
can just add User ID to the table that stores these query definitions and
that would provide a means for retrieving that user's queries.

That should work. I guess it didn't really occur to me because it's user-
specific and I think of a backend as providing data to all and not
necessarily holding individual user preferences.

Thanks!

The query definitions are stored in tables in your back-end database.
Changing the front-end will have no effect on the previously designed
queries/reports.

Duane:

[quoted text clipped - 19 lines]

to
keep them from being lost during an update.