How to store options ?

[Mihail]

Hi all !
I have an unbound form with some controls (check boxes and option buttons) where I make some settings (i.e. AutomaticPrint - checked or unchecked check box, ReportToPrintName - option buttons and so on).
I need to store the user options for further use (in the next work session).
Of course I can store this options in a .txt file but Access is designed for databases, so I think that must be a way to store this options in a table.
Can you help me with some advices or/and some VBA code for that ?
Thank you !

[Adam Tippelt]

You could create a table where each column matches each option you have on the form.

Add some form of "Save settings" button to the bottom of the form, which triggers something like this:

Private Sub cmdSave_Click()
On Error GoTo cmdSave_Click_Err
Dim db As DAO.Database
Dim rst As DAO.Recordset
 
Set db = CurrentDb
Set rst = db.OpenRecordset("YourSettingsTable")
 
rst.AddNew
rst!AutomaticPrint = Nz(Me.AutomaticPrintControl,0)
rst!ReportToPrintName = Nz(Me.ReportToPrintOptionFrame, 0) 'Stores the option 
rst!Setting3 = Nz(Me.YourCheckBox, 0) 'Stores whether the checkbox was ticked or not. Ticked = -1, Unticked = 0.
rst!Setting4 = Nz(Me.YourOptionFrame, 0) 'Stores the option value.
rst.Update
 
End Sub
 

That should allow you to store the settings in a table instead of a .txt file.

If you add a field in to store the current user as well, you could couple this code with a way of automatically reloading the current saved settings for the current user, and also a dlookup on the save button that checks the user field, if settings don't exist for the current user, rst.addnew, else rst.edit.
It really depends on how your system is designed and what functionality it includes.

Hope that helps.

Adam.

[NeoPa]

You're absolutely right to think that way Mihail. Many overlook that simple point.

It may sound very simple, but the answer is to bind the form to a table. This can be a control table if you like. You can filter it if you want a specific record from the table. Often, databases exist with a control table which contains a single record to manage overall database settings.

[Mihail]

Thank you both for answers.

Adam, I do not think as far as you teach me. With my database can work anyone, but is very useful to me your idea. I think I'll try to implement it in a next version.
Thank you again.

If someone else has new ideas please, let me know.

[Rabbit]

I'm not sure what you mean Mihail. Adam's suggestion will work for "anyone" as you put it.

[Mihail]

Rabbit, is my english. Sorry for that. I mean that I do not implement users to my database. If I, you or anyone else open my database, can work in it (in database) without passwords or other troubles.
Even now I am not sure that I explain OK, because I learn english from the computer's help files so...
Adam's reply solve my question, but if anyone else has more suggestions he (she) is welcome.

Thank you for your interest.