Saving settings in VB programs.

[Keithuk]

Don't use SaveSetting and GetSetting that just puts c*** in the registry. If you uninstall your app then this c*** is left behind. Use an ini file, if your app is setup correctly then it can check to see if the values received from the ini are valid. And you don't have to use Yourapp.ini it can be Yourapp.dll.

[Hack]

Don't use SaveSetting and GetSetting that just puts c*** in the registry. If you uninstall your app then this c*** is left behind. Use an ini file, if your app is setup correctly then it can check to see if the values received from the ini are valid. And you don't have to use Yourapp.ini it can be Yourapp.dll.

Actually, I've gotten away from using either the .ini file (which I haven't used in years) or the registry. I include a CUSTOM_SETTINGS db table with my application and save all of those things that would be a registry setting or an .ini setting in a table.

[MartinLiss]

An interesting article.

[Dave Sell]

An interesting article.

Yes, it is interesting. The author provides some examples of "flaws inherent to INI files". This is a mis-speak, those are limitations of the Win32 API, not INI files themselves. Text files are not limited to 64Kb, and you can make entries as long as you want.

[MartinLiss]

...you can make entries as long as you want.

Can you use such things as WritePrivateProfileString with entries longer than 256?

[Dave Sell]

Can you use such things as WritePrivateProfileString with entries longer than 256?

Possibly, but my point is that this is a limitation of the Win32 API, not of INI Files.