I tried the trial out on my workstation and everything installed swimmingly, loved the product, and we're purchasing DBXL. Now we're trying to install it on our servers so that we can start using it in production. But, I am a little confused by the language in your installation guide.
To me, a client is a desktop that accesses something on the server. However, it seems that the client for DBXL is the piece that wants to tie into a web site for publishing the web service. Which, in this instance, would make my web server the client? If this is true, does that mean that I have to put InfoPath (a non-server application) on my web server? I mentioned this might be the case to my boss and the network admin, and they were less than pleased. I'm getting a vague error on installation in the event log ("Product: Qdabra Database Accelerator v2.4 -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2869. The arguments are: ErrorDialog, , "), but I do not currently have InfoPath on the web server so that could be the problem. I was rather hoping there'd be a way to have the DBXL web services exposed on the web server without having to install InfoPath on it.
When it gets to the installation screen about selecting a web site, is there a way to have it point to a web site that's not on the computer you're installing it to? That way I can install the front end that uses InfoPath to manage things on my desktop, tie the web service to the web server, and have the SQL portion to our SQL Server. I can't seem to find a way to do this as it appears that the drop down only wants to let you select websites from the IIS on the computer you're running the installer on.
The environment is SharePoint 2010, InfoPath 2010, IIS 6.1, .NET framework for site is v2.0.50727, SQL Server 2008, all server OS's are Windows Server 2008 R2 Enterprise, and I am trying to install it on a web server that is NOT running our SharePoint site; we want to keep that separate. Thank you for your help and for making such a great product to fill InfoPath's holes, I look forward to hearing from you.