>>two version of the same module...
The point is, using this method, I don't have two versions of the same module. All dvb's access the common module for what they need, instead of duplicating it over and over. Its like having a common dll.
If you still MUST use vss, export the modules from the dvb (they will get saved as bas and cls files) and then bring them into vss for comparison. I havn't tried it though, but I believe that would be your only way.
--
----
Ed
----
"Davids" wrote in message news:40e5314b$1_1@newsprd01...
Thanx Ed...
This may be a small solution, but you don't may evaluate the difference
between two version of the same module...
In the add-in manager i see the VSS add-in link but after her start the
login dialog don't see the VSS database... There's a additional component to
install to work?
Also Access is a unique file, but the VSS add-in split this file in more
files and these files are added to VSS...
Autocad may work similary?
Davids
____________________________________________________________________________
___
"Ed Jobe" wrote in message
news:40e43047$1_1@newsprd01...
In VS, modules are separate files. In vba, they are compiled into a dvb,
so...no. Unless you export everything in your dvb. When I want to share
modules in acad vba, I just created a Toolbox.dvb and reference that dvb
from the other dvb's. The only other caveat, is that, for Intellisense to
work, you need to qualify the whole object heirarchy. Whereas, when the
function was in the same project, you only had to specify the function's
name. Now, when the function is outside the project in another dvb, you need
to specify a fully qualified name, fqn, using the syntax,
Project.Module.Procedure.
--
----
Ed
----
