Subject Re: Big Mistake From Andy Taylor <andy.taylor.1959@outlook.com> Date Fri, 16 Sep 2022 12:00:44 +0100 Newsgroups dbase.getting-started Hi Bob, I have an answer for you which Ronnie MacGregor pointed me towards first thing this morning so I haven't even had to think too much yet today. I should also thank Ken Mayer for suggesting that custom form classes might be the problem, which I confirmed last night by screwing up my copy of dBASE. :-) You have a couple of rogue entries in your dBASE ini file which need to be removed. My entries won't be the same as yours but don't worry, all you have to do is remove them. My entries put in last night by dBASE were: [FormDesigner] BaseFormClassFileName=D:\Develop\SandBox\proddisc.dmd BaseFormClassName=ProdDiscDATAMODULE They have now been changed to: [FormDesigner] BaseFormClassFileName= BaseFormClassName= My system is now back to normal. The easy way to get into your inifile is to open your dBASE command window and enter the following command: modi comm (_app.iniFile) That will pull up the source editor. You need to find the problem entries for the [FormDesigner] section and remove them. Then close the source editor, electing to save your changes. Now close dBASE. Restart dBASE... all should be back to normal. If not, try the above process again. Please let us know how you get on. Andy