We are working with a new communications vendor, and they asked for a listing of tables, fields and the relationships among each table. Since RE is proprietary and they don't own the software, is there a way to print out the structure in a tree form, or even export the tables, etc. to an Access database?

Why on earth would your communications vendor even be interested in the database structure?  What are they trying to do where this information would even be relevant?

Drew

If they are a vendor that is familiar with RE then what they likely only need are the structure of your custom tables.  You can go to config - tables and right click to print and get them the code tables report for any tables they want.

If they are unfamiliar with RE I would hesitate to give them too much and be careful not to pay hourly time for them to learn it.

 Thanks. I don't plan to give away the store! I think they just want to know how we are using RE and if we are using it to its full capabilities. I don't know how familiar they are with RE, but they've worked quite a while with many NPs, so I'm sure they've come across it a few times...the structure of the code tables will probably sufficient.

It just seems to me that your communications vendor is overstepping their bounds.  As I understand it, a communications vendor should be dealing with the physical infrastructure, such as networking and telephony, for your business operations.  The fact that they are asking about something that has no apparent relevance to their function raises all kinds of red flags.  I would want to know exactly what they were planning to do with the information before I would even consider giving it to them.

Part of it, too, is that the back end is hopelessly complex.  Looking at the back end is definitely not the best way to determine if you are using RE to its full capabilities.  Here again, knowing exactly what they are trying to accomplish will help to provide the best answer.

Drew

I just did a tour of CISCO and saw a bunch of their new technology so perhaps your vendor is trying to move in that direction? Things like how RE and OUTLOOK communicate with your phone system, etc. (example: having voicemail translate into email and then becoming an action in RE on a record)  This is just a wag.. but I thought I'd take a stab. I would discuss scope with them and make sure they are aware that it's a proprietary system, etc.

If that is the case, then they shouldn't be looking at the back end at all.  They'll need to use the API or risk invalidating your maintenance contract.

Drew