Ian,
I’ll try to be more specific as the issue isn’t the database type.
I have a multi-user project using a SQL back end.
Sparx Security is enabled. User Logins linked to AD accounts.
Multiple Root packages in the project supporting multiple capital project with a shared core architectural base.
Document Management is enabled.
Documents are stored external to Sparx using a UNC path.
EADocX Documents in a separate Root project with Documents and People packages contained in the Root.
For EADocX to work, it appears to require a lock at the Documents package level. This limits the project to one user running an EADocX document generation at a time.
Is this the expected behavior? Is there a better practice for using DM on projects which have Sparx security enabled?
