Hello,
for better file handling I am thinking about changing from INI-files to dbf-files as program setup files.
Could there be a problem with dbf-files using as setup files?
Thanks in advance
Otto
Hello,
for better file handling I am thinking about changing from INI-files to dbf-files as program setup files.
Could there be a problem with dbf-files using as setup files?
Thanks in advance
Otto
Otto
I have an Enterprise application in State government that is used from different regions through out the State. The application knows nothing about the regional location, so I have no other way of identifying each unique location other than to use a modified .ini . It would be almost pointless to associate a user by location since that user could potentially login from anywhere in the State.
I agree an .ini can be a bit clumsy, but in this case it was the best solution.
Rick Lipkin
Personally, I have always used in configuration files, the INI files
Otto wrote:Hello,
for better file handling I am thinking about changing from INI-files to dbf-files as program setup files.
Could there be a problem with dbf-files using as setup files?
Thanks in advance
Otto
I think the best way is to use SQLite and you can Encrypted the table
At first you detect if it exists if you can not create it and from your application as Enrico says "all settings is done through the application"
Regards
I use INIs with values of keys encrypted
Hi,
Ini files work well for basic application configurations, grid colors, window position, ... which are even easy to manipulate from any editor outside of the application, but in the case of configurations for example referred to user is better in tables.
When you design the maintenance from the tables, at the end you put everything in a parameter table, public and private parameters.