Is Combo Box right for keeping track of input?

[djj55]

Hello,
I have a form (Access 2002) that is used to look-up values in my database (this is a simple explanation as to what this form does).

The user wants to keep a list of searched values for the session. This will be used to go back to a previous look-up.

Example: User wants account 123, then goes to account 456, then wants to go back to account 123.

Because the entered value is 10 to 20 characters they do not want to re-type.

I would like to use a combo box for this but am unsure how to handle the addition to the box. If I close the search form is there a way to keep the list?

Thank you,
djj

 

[Remou]

Why not add the searches to a search table with a date and time? This would be easy to load into a combo. The table can be updated with the current date, if the search already exists, or you can append, if it is a new search. The user can be offered a list in descending order by date/time.

 

[djj55]

Thank you for your reply.

With 80 users I would need a table that included the user. That is not a problem. What is the problem, is how do I dump the data after the user quits the program?

Since the user can not be depended upon to exit the program in a given way (gee, let me reboot), how do you delete the records for the session?

Thanks
djj

 

[PHV]

Why deleting the records for a session ?
Delete old records in the LoadEvent procedure of the form.

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[JBinQLD]

Gday fella,

If each user has own front end store the records in a local table so their own front end shows only their searches?

Problem 2: On startup get your autoexec macro to set warnings to false then run a query that does "DELETE mytable.* FROM myTable"

Sounds like a nifty little feature, I can think of a client that would benefit from a similar system - thanks for the idea!

JB

 

[djj55]

Hello,
Thank you for the replies.

One front end for everyone.

Thank you for the delete on the startup. That is what I needed.

djj

 

[Remou]

One front-end for everyone."

I really hope you don't mean that, it is asking for trouble:

http://msdn.microsoft.com/en-us/library/aa167840.aspx

 

[JBinQLD]

OMG, I misread until Remou pointed that out! Just as a perfect example of why one front end is such a bad idea, think about what we just discussed - each time a user starts the database the search list is gonna be reset. How confusing will that be? And with 80 users it will be carnage!

 

[djj55]

Hey if it were up to me there would be a .NET solution but with the CIO creating the Access front end several years ago I have to use it.

We are trying to move to the .NET but they go kicking and screaming.

djj

 

[JBinQLD]

No offense intended mate, but couldn't each user have their own copy of the front end regardless? I'm sure it would help.

JB

 

[djj55]

If the database did not change frequently I would agree. As I am not the person who pushes updates I am told it is hard (but I have pushed updates easily).


djj