mmm, well this could be the result of corruption in your slickedit state file (vslick.sta or vslick.stu), corruption in your project file, corruption in your installation executables, corruption in your operating system or your computer's just having an off day.
I don't really know what you mean by add dependencies but if this is something that has worked before and has just started having a problem it is probably a problem with your state file. Maybe you could try creating a second new project and see if you get the error. If so, try creating a new configuration folder by invoking slick with the -sc switch - i.e. when you start slickedit, use vs.exe -sc some-new-empty-folder. Slick will then create a new configuration folder for you containing a new "virgin" state file (a copy of rescue.sta from the installation folder I believe). Try creating a new project. If the problem is gone you can either persist with the new configuration folder, or you can do the following
1. close slick and backup your configuration folder
2. delete vslick.sta from the configuration folder
3. restart slick. It should create a new state file and try to keep your configuration settings.
BTW - the state file contains (amongst other things) a large amount of "p-code" which is executed by the slickedit interpreter. Whenever you save your configuration settings, the state file gets rewritten so if part of memory has been corrupted, the state file might get some bad data written to it.
Graeme
Forgot to mention, if the name of the file you add to the project is //*, slickedit might crash completely - at least V15.0.1 does if you call project_add_file with //* as the filename!
