I have an application with several Databases and forms and made specially to work on Client / Server platform. In order for it to adapt to various setups without changing the codeing, I have made one database with only one record having various printer names, server and client names, various option as to one wants to print with option to preview with various forms, whether want to select the printer before printer with various printing chores, level One users List, Level two users list (in order to contorl accessibility), etc. I named this database and form setup that has also made part of the application.

Since it contains only one record, I get the relevant info using @xResultsetcommand ( ) whenever I want to get those values from the setup database. It works. However, I believe, there has to be a better way. May be something like setup.ini file and getting all the value in the globalvalue  variables so, it can be available all time and do not have to called in @xResultSetCommand () to get the value.

What is the code for reading .ini text file, to remove //comments etc. and form a string of value and getting them using @AccessStringArrary ( )?  How one would use .ini file to achieve the goal?

Any ideas? Any suggestions?  Thanks.

Thanks Erika. I can either parse text file with format just like sesame.ini file and form the @GlobalValue () for each entity on the file, like

PrevewPrescription = Yes

Globalvalue ("PreviewPrescription", "Yes")

and then in the code, I can use it like

if @Globalvalue ("PreviewPrescription") = "Yes" then
       {

        }

I can do the same thing by picking up the value from Setup database and assign them to respective Globalvalue variable, Name of the Element becomes the Globalvalue ( ) name and value of the element becomes the value of the GlobalValue ( ) variable.

Making and loading 15 to 20 global variable...  How much resources does the application use. Is it practical?

With Database option, my file is protected and nobody can manipulate it.

Which one is better and practical way to go?

Your advice is very much appreciated.

Unless you are writing a book in each of them, 20 GlobalValues is a very small number. Performance will not suffer by their presence.

You can only get rid of them by deleting them in Designer and reconciling. You can set them to blank values in runtime, but you can't delete them. There's really not a need to do so. Having them there does no harm, especially for such a small number of them.