Hi Matthew,

> Hmm, I think I'd double check that the session components are indeed
> not duplicated. There must be something that the IDE is doing, or not
> doing, that is causing this. Do you have datamodules referenced from
> forms, or inheritance at all? Datamodules and inheritance cause me
> trouble in some of my projects as the IDE tells me that it cannot close
> something because it is linked by a form that is open, even though it
> isn't really open but is because of the inheritance and a form that is
> open. I find I have to close everything, then the IDE, and then I can
> edit the thing I'm wanting. (Details fuzzy because it is a while since
> I worked on that.)

I know what you mean here (I've hit similar issues), but this is not the
case in this instance. This same project can be opened in Delphi 2007
without issues. (It also wasn't an issue until I updated to the latest
Hotfix in XE2).  If what your referring to was the case, then I would
expect it to happen regardless of what version of Delphi I had open.


> Anyway, the simple answer is that DBISAM doesn't have a problem in
> general, so there is something about your setup that is causing this.
> If you can pin it down, then we can perhaps suggest ways around it, but
> keeping it inactive would help (as Roy says, there are add-ins that can
> de-activate database components on save).

Thanks. At this stage I think I'll just use Roy's work around. I'll
probably be rebuilding / creating a new development virtual machine when
Windows 10 comes out, so with any luck the problem may just disappear /
fix itself with a clean installation of Delphi and patches.

Cheers

Adam.