469,623 Members | 1,800 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,623 developers. It's quick & easy.

Saving Query Strings

I have an interface that works with an Access back-end. I would like to
store and/or load user defined query strings per each user (i.e. no user can
access another's queries). The idea I had was a "table" stored with the C#
front-end (not in the Access database), but don't know if this is even
possible. If it is, can someone let me know how? Otherwise, how do other
people handle storing and loading query strings for possible later use?
Mar 14 '07 #1
3 1566


"Nathan Guill" <NG****@Forgeman.comwrote in message
news:ep**************@TK2MSFTNGP05.phx.gbl...
>I have an interface that works with an Access back-end. I would like to
store and/or load user defined query strings per each user (i.e. no user
can
access another's queries). The idea I had was a "table" stored with the
C#
front-end (not in the Access database), but don't know if this is even
possible. If it is, can someone let me know how? Otherwise, how do other
people handle storing and loading query strings for possible later use?

Is this for an ASP.Net application? WinForms app? For ASP.Net, I would go
with defining a table within the database that contained such strings. For
the latter, I would go with defining a custom configuration file per user
that is stored within the user directory of the current user. All in all
though, I probably would not be storing such strings anywhere. Depending on
your requirements, you may be able to go about this without using "custom"
query strings.

What is it exactly that is "custom" about these query strings that can't be
made static with additional parameters?

HTH,
Mythran
Mar 15 '07 #2
Sorry, It's for a WinForms app.

I was just thinking that the user might want to save a query that they run a
lot, but is not something I have been asked to develop a standard for. This
way they do not have to reenter the search criteria each time. But now that
I'm thinking about it, these forms are not showing that much data to begin
with, so I think I'm going to leave this capability out as I don't think it
would be that big of a hassle for the user to do...

"Mythran" <ki********@hotmail.comwrote in message
news:03**********************************@microsof t.com...
>

"Nathan Guill" <NG****@Forgeman.comwrote in message
news:ep**************@TK2MSFTNGP05.phx.gbl...
I have an interface that works with an Access back-end. I would like to
store and/or load user defined query strings per each user (i.e. no user
can
access another's queries). The idea I had was a "table" stored with the
C#
front-end (not in the Access database), but don't know if this is even
possible. If it is, can someone let me know how? Otherwise, how do
other
people handle storing and loading query strings for possible later use?

Is this for an ASP.Net application? WinForms app? For ASP.Net, I would
go
with defining a table within the database that contained such strings.
For
the latter, I would go with defining a custom configuration file per user
that is stored within the user directory of the current user. All in all
though, I probably would not be storing such strings anywhere. Depending
on
your requirements, you may be able to go about this without using "custom"
query strings.

What is it exactly that is "custom" about these query strings that can't
be
made static with additional parameters?

HTH,
Mythran


Mar 16 '07 #3
Does he write his own query, or select stuff on the screen?

I have written a few apps that provide my users with the ability to run ad
hoc requests against the database. I have a bunch of selection criteria on
the screen that they fill in. I create the query, run it, and return the
data to them.

If you are doing that, you can save the values of all of the controls using
My.Settings in VB (it's also in C#, but has a different name; post back if
you need it), then reload them when the user comes back in. That's what I
do.

If they are actually crafting queries, I would do the same thing. I would
save them to My.Settings and then fill it back in.

Anything you can do to make your users' lives easier makes you look better.
It's the small things that count in an application. I once got kudos from a
top-level manager because I used masked edit boxes for the dates, and he
didn't have to type the slashes. Haha!

If you want more info on saving settings, post back with your language of
choice, and I'll post some code for you.

Robin S.
-------------------------------------------
"Nathan Guill" <NG****@Forgeman.comwrote in message
news:O0**************@TK2MSFTNGP02.phx.gbl...
Sorry, It's for a WinForms app.

I was just thinking that the user might want to save a query that they
run a
lot, but is not something I have been asked to develop a standard for.
This
way they do not have to reenter the search criteria each time. But now
that
I'm thinking about it, these forms are not showing that much data to
begin
with, so I think I'm going to leave this capability out as I don't think
it
would be that big of a hassle for the user to do...

"Mythran" <ki********@hotmail.comwrote in message
news:03**********************************@microsof t.com...
>>

"Nathan Guill" <NG****@Forgeman.comwrote in message
news:ep**************@TK2MSFTNGP05.phx.gbl...
>I have an interface that works with an Access back-end. I would like
to
store and/or load user defined query strings per each user (i.e. no
user
can
access another's queries). The idea I had was a "table" stored with
the
C#
front-end (not in the Access database), but don't know if this is even
possible. If it is, can someone let me know how? Otherwise, how do
other
people handle storing and loading query strings for possible later
use?


Is this for an ASP.Net application? WinForms app? For ASP.Net, I would
go
>with defining a table within the database that contained such strings.
For
>the latter, I would go with defining a custom configuration file per
user
that is stored within the user directory of the current user. All in
all
though, I probably would not be storing such strings anywhere.
Depending
on
>your requirements, you may be able to go about this without using
"custom"
query strings.

What is it exactly that is "custom" about these query strings that can't
be
>made static with additional parameters?

HTH,
Mythran



Mar 17 '07 #4

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

3 posts views Thread by Michael | last post: by
2 posts views Thread by jim_geissman | last post: by
7 posts views Thread by MacDermott | last post: by
4 posts views Thread by ulaskaraoz | last post: by
2 posts views Thread by Tal Shachar | last post: by
reply views Thread by devrayhaan | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.