Glenn,

After some more testing I found that this solution doesn't work in the program editor. When I tested this yesterday, I only tried it in the command window where it works. Unfortunately, in the program editor, CEE is still activated eventhough the settings "spaceBar" and "commandWindow" are set to "No". I also have an empty expand.dbf. The problem is that CEE interferes with intelliSense and intelliSense is not available anymore :(

Too bad. I'm still waiting for a response from COB. As I said earlier, I will post a message if get a solution.

>Hi Daniel,
>
>You can switch your Macro expansion files based upon your working environment. If you use an envirnment setting program add code like this to exchange the expand files.
>

>#include foxpro.h
>#DEFINE HKEY_CURRENT_USER           -2147483647  && BITSET(0,31)+1
>
>LOCAL lcLocalPath, lcFile, oReg, lcTeamPath
>
>IF NOT EMPTY(SYS(2000,(_samples+'Classes\registry.prg')))
>	set PROCEDURE TO (_samples+'Classes\registry.prg')
>	oReg = CREATEOBJECT('registry')
>	IF VARTYPE(oReg) = 'O'
>		IF VERSION(4) < '07'
>			lcFile = 'Expand7.DBF'
>		ELSE
>			lcFile = 'Expand.DBF'
>		ENDIF
>		lcLocalPath = ''
>		oReg.GetRegKey("LocalExpand",@lcLocalPath,;
>					"Software\COB\CEE\6.0\Options",;
>					HKEY_CURRENT_USER)
>		lcLocalPath = JUSTPATH(lcLocalPath)
>		lcTeamPath = ''
>		oReg.GetRegKey("LocalExpand",@lcTeamPath,;
>					"Software\COB\CEE\6.0\Options",;
>					HKEY_CURRENT_USER)
>		lcTeamPath = JUSTPATH(lcTeamPath)
>
>		oReg.SetRegKey("LocalExpand",lcLocalPath+"Expand7.DBF",;
>					"Software\COB\CEE\6.0\Options",;
>					HKEY_CURRENT_USER)
>		oReg.SetRegKey("TeamExpand",lcTeamPath+"Expand7.DBF",;
>					"Software\COB\CEE\6.0\Options",;
>					HKEY_CURRENT_USER)
>	ENDIF
>endif
>

>
>
>
>>Craig,
>>I guess I could. At the moment I'm converting all the IDE tools, add-ons, etc. from VFP6 to VFP7. I've extensively used CEE and in order to convert all of its functionality to VFP7 I need to compare between the two versions. Unfortunately as I mentioned to Rick, it seems impossible to have two different configurations. I've sent a message to the CEE support to see if there's a workaround. I'll post a message here if I get a solution.
>>
>>
>>>>
>>>>Thanks Rick. I will probably use CEE as you suggested. Unfortunately it seems impossible to have two different configurations for CEE since the settings are stored in the registry. At the moment I still use VFP6 and want to use the full functionality of CEE. I could use an empty expand.dbf in VFP7 but am afraid that CEE may interfere with intelliSense if it's not deactivated.
>>>>
>>>
>>>I've been using VFP7 for all my coding and VFP6 to test and run for several months now. Any reason you can't do that?