slinky
asked on
Using RDO, Enterprise V Professional
We would like to use RDO on our project made up of 4 developers. Do we need to have a copy of Enterprise for each developer or is it possible to use Professional for those developers not writing the RDO parts of the code and simply integrate on the Enterprise machine?
Also, if there are any other issues regarding the use of RDO (distribution, licensing etc) then I would be delighted to hear about them.
Not a difficult question I'm sure but I'll give 200 points to encourage a swift response!
Also, if there are any other issues regarding the use of RDO (distribution, licensing etc) then I would be delighted to hear about them.
Not a difficult question I'm sure but I'll give 200 points to encourage a swift response!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I have created a setup for one RDO project using InstallShield, and it seems to work fine. Unfortunatly, it isn't ready for distribution yet, so I don't know how it's going to react on another person's machine. However, I did check with someone else familiar with RDO, and they said that it contained all the proper files.
As far as being a supported feature, that's hard to say. RDO will work in any Version of VB (Learning, Professional, Enterprise). It's just a matter of having the license files for the component. Most of the license files are not included with Learning. However, it's been my experience that when a component is not supported from one version to the next, it won't even be available for insertion into a project without displaying an error message. Probably the best way to test this is to create a simple project that just opens and closes a database with RDO. Create a setup and install it on a machine that doesn't have anything of VB on it. If it runs, then you know it works.
As far as being a supported feature, that's hard to say. RDO will work in any Version of VB (Learning, Professional, Enterprise). It's just a matter of having the license files for the component. Most of the license files are not included with Learning. However, it's been my experience that when a component is not supported from one version to the next, it won't even be available for insertion into a project without displaying an error message. Probably the best way to test this is to create a simple project that just opens and closes a database with RDO. Create a setup and install it on a machine that doesn't have anything of VB on it. If it runs, then you know it works.
ASKER
So, on balance, 1 Enterprise and 3 Professional should cover all eventualities?
It seems to me that it would. If you develop a module in Professional, and find out that it needs some RDO code, then if nothing else, you can simply move it to the Enterprise machine to finish coding it. There's nothing to say your programmers can't rotate machines if the need be. But if only that particular module needs the RDO code, then I don't think even that eventuality would come up. What you might consider is creating a class that encapsulates your database with RDO, then expose properties and methods of that class so the programmers with Professional can access the data through that class. That would allow you to have your data avaliable through RDO to any part of your project, regardless of where it is being developed.
ASKER
Sounds good to me!
ASKER
Do you know if RDO working in Professional is a supported feature and not just a fortunate occurence?
I need this to be a watertight development and distribution environment.