References: Going to a newer version

[Dymondjack]

Hello again and thanks in advance, as always.

This is a new area for me... Per the suggestion of a selection from my
library of educational books I have tried to set a reference to Microsoft
Active DataX Objects 2.7. Currently selected, and has been since I started,
is a reference to DataX 2.1. When I try to set the reference to 2.7 I get
this error "Name conflicts with existing module, project, or object library."
Due to my inextensive experiance with references and how they 'actually'
work, this brings up the following questions:

1) I would think that you would be able to switch to a newer version of a
reference without jepordizing any existing code. It seems rather ludicrous
that whatever reference version you start designing a database with is the
one you're stuck with for the remainder of the project without backcoding.
Am I correct in the assumtion that this is possible?

2) Can I deselect the current v2.1 and then select v2.7 without having any
effects to my current code? I'm thinking that possibly the 2.7 won't go
because the 2.1 is already selected. I do have a (many) backups of the db
I'm working with, but am more concerned with long term effects that might not
be immediately visible, and I would hate to find out after yet another 30
hours of coding that I have to go back and do it again.

Any light shed in this subject would be a great help. Thanks

 

[Douglas J. Steele]

You can't have multiple references to ADO. Removing the existing reference
and adding the new one will not impact your existing code in any way.

Think of a reference as being similar to a module. You could have a function
defined in a module, and call that function from all sorts of other forms
and modules. Removing the module that contains the function wouldn't impact
any of those other forms and modules. Of course, if you tried to compile the
application, or to run it, you'd get errors because of the missing function,
but adding it back in would eliminate those problems.