We have a legacy Quote and Work Order application that batch reads Customer records from Adagio into an offline table within our database. We are in process of rebuilding this application as a Web App and need to understand the limitations/restrictions associated with running Adagio OBDC on a Windows 2008 Server.
Question 1: are there license issues?
Question 2: Will it function on Windows Server 2008?
Question 3: Assuming all is well, which version is required
Thanks...

Hello Christine,

If the records are moved to the external table as a batch, then I'd STRONGLY suggest using Adagio GridView to create an Excel table of the data you need. This pocess is way easier to debug, and Adagio GridView can be scheduled to create the table whenever you want.

The licensing "issues" (such as they are) are the same for both products. However, your user community will find GridView a useful tool in its own right, while ODBC is very strictly a programmer's tool.

Bruce Gardner, who monitors this forum, has experience with both products. Steve Schwartz has several sites running complex GridView processes overnight. Same for Doug Dickie and Brian Stief.

Hello Christine:

Questions for you:
-Are you already using ODBC with the legacy application?
-If not, how are you extracting the Customer data?
-How often during the day do you extract data?
-In a batch or on an as-needed basis?
-What Customer information do you extract beyond basics like address?
-Do you already own GridView?
-Can you easily read up an Excel file?

As to your questions, ODBC will use an Adagio license when it connects (although if this is an overnight process, that won't put any strain on your license count). I have at least one client using Adagio ODBC on Windows Server 2008 so that is fine. The current version of ODBC is 9.0A (released July 31, 2008). You should be using that version if you choose the ODBC route.