Licensing...

rbuser

I need a couple licensing clarifications:

1. If I create some isapi or cgi scripts that allow reports to be run
through a browser, is there any additional licensing necessary? These
scripts will be specifically geared towards reports for our system, and not
capable of running just any off-the-shelf RB report. The scripts will be
distributed to end users or our software, allowing them to run reports on
their intranet/extranet.

2. Our software is similar to a CRM system. We have two main dbs that store
global data and allow users to create additional dbs for projects. Our
reports dynamically create connections to these user dbs at runtime to
gather data. We would like to offer the design interface (including RAP) to
our end-users, but are concerned about the "one database" licensing
limitation. We can certainly limit the end users db selection to only those
that are involved with our system, thus removing the possibility of a
generic report writer. In addition, even our core data is stored in 2
separate dbs, also giving rise to our concern for the one database licensing
limitation. Can this type of design fall under the current licensing, since
we are not creating a standalone reporting tool?

Thanks,
Paul

nardmoseley

1. Not a licensing problem. From a performance, quality perspective I
recommend that you consider using RB Server Edition.

http://www.digital-metaphors.com/RBServerLive

http://www.digital-metaphors.com/products/report_server/architecture.html

2. If you need to connect to two fixed databases that is ok. I do not quite
understand the meaning/context of "We can certainly limit the end users db
selection to only those that are involved with our system." What databases
are those?




--
Nard Moseley
Digital Metaphors Corporation
http://www.digital-metaphors.com

rbuser

Our application allows users to create dbs through our interface for CRM
projects, like marketing campaigns. They can create an unlimited number of
projects, which means an unlimited number of dbs. We store connection info
for each project db in a table in our application db. Our RB reports read
the connection info at runtime and gathers data from all user-selected
project dbs.

The statement "We can certainly limit the end users db selection to only
those that are involved with our system." refers to limiting the list of
datasources/dbs in the designer to those that have been created through our
application or are specifically involved in our application. Doing it this
way would give the user the ability to edit/modify our existing reports, and
be able to create their own reports based on the data from their project
dbs. They would not have the ability to create reports based on a db from
some other source, such as another CRM system or another db platform. They
could only create reports from our two main dbs and their project dbs.

Thanks,
Paul

nardmoseley

Sounds like its an unlimited number of db's with an identical proprietary
schema used by your application. That would be ok. That adheres to the
intent of the license.



--
Nard Moseley
Digital Metaphors Corporation
http://www.digital-metaphors.com

rbuser

You are correct that the schema is identical accross the dbs.

I appreciate the clarification and confirmation of the licensing.

Thanks,
Paul