Subject Re: dBAse 11 Exec.ini Files From Akshat Kapoor <akshat.kapoor@kapoorsons.in> Date Wed, 17 Jul 2019 19:52:43 +0530 Newsgroups dbase.getting-started On 17/07/2019 17:20, Ken Mayer wrote: > On 7/17/2019 12:29 AM, Akshat Kapoor wrote: >> On 17/07/2019 09:10, Norman Snowden wrote: >>> Ken Mayer Wrote: >>> >>>> On 7/16/2019 12:49 PM, Norman Snowden wrote: >>>>> Dbase 11 Exec.ini Files >>>>> >>>>> Previously using Project to Build and Save an Executed version of a >>>>> Form the Exec.ini File would automatically appear >>>>> in the Folder alongside the Saved Application. >>>>> >>>>> Now only the Application appears. How can the ini file be viewed to be >>>>> sure it is what I want it to be? I can find the dBASE Plus 11 ini >>>>> File but not the ini file my Executed.exe is using. >>>> >>>> Add some code in the startup routine of your application and >>>> recompile it: >>>> >>>> msgbox( "ini file: " + _app.iniFile ) >>>> >>>> This will give you the exact path ... by default dBASE Plus 8 and later >>>> uses the Windows UAC for storing files, and that includes using the >>>> user >>>> folders and more. >>>> >>>> Ken >>>> >>>> -- >>>> *Ken Mayer* >>>> Ken's dBASE Page: http://www.goldenstag.net/dbase >>>> The dUFLP: http://www.goldenstag.net/dbase/index.htm#duflp >>>> dBASE Books: http://www.goldenstag.net/dbase/Books/dBASEBooks.htm >>>> dBASE Tutorial: http://www.goldenstag.net/dbase/Tutorial/00_Preface.htm >>> >>> Thanks Ken, >>> >>> The path given was  ini file:c:\users\N\AppData\Local\dBASE\Plus >>> 11\Bin\Plus.ini >> >> Just a word of caution. >> This is dBase ini file and not your exec.ini file. >> For that you would have to run the same command from within your >> executable. >> It just shows the ini file the current exe (dBase in this case) is using. > > Wrong. _app.iniFile is the file that is in use by the current > executable. If you do this from the IDE, it is the one being used by > dBASE Plus. If you do this from your own executable, it is the one being > used by your executable ... Sorry for being unclear. This is what I meant when I wrote "For that you would have to run the same command from within your executable." Regards Akshat