Eval function with variables

[tuna]

Hi, is it possible to use the eval function with variables e.g. Eval("foo + bar") or Eval("""The value of foo is "" & foo")?



This is because I have my database settings in a table (one field having the name of the setting and the other containing the value) and I wish to be able to reference variables in the settings value. E.g., for the "MsgOnExit" setting, I would have the string

"Are you sure you would like to exit " & AppTitle

Where AppTitle is the name of the database. I would then plan to use Eval at runtime to evaluate the expression to resolve AppTitle to a value. Of course, this may not be the best example as many would argue AppTitle should be a constant, but there are other settings which rely more heavily on variables being able to be resolved at runtime.

(I'm using a settings table because it allows for a settings GUI and also the ability to variables across sessions.)

Thanks

[pbaldy]

I don't see that you need the Eval() function at all. Get the value into a variable from the table using your method of choice (DLookup, recordset) then your method works fine:

MsgBox "Are you sure you would like to exit " & AppTitle

[tuna]

Thanks. However, I need a way to reference a variable at runtime, not just retrieve it's value at the start since I would need to allow it to change. OK, my previous example probably wasn't very good since AppTitle is supposedly constant throughout each session. I need something like mySetting = foo + bar, where foo and bar are variables that can change during runtime.

So might you think, why not take into account variable changes by updating the settings table with the changed value? But since my database will be accessed by multiple users I can't write session-specific settings to table (e.g. many "counting" variables) without affecting all users.

Thanks

.

[pbaldy]

Perhaps I'm not understanding what you're trying to do. If your application is used by multiple users, it should be split. In a split application, each user would have their own copy of the front end, so a table in the front end for users settings/selections would allow users not to conflict with each other.