Cameyo

Members Login
Username 
 
Password 
    Remember Me  
Post Info TOPIC: Virtual app connecting to different databases


Newbie

Status: Offline
Posts: 2
Date:
Virtual app connecting to different databases
Permalink   
 


When we create a packaged app (executables only - no database) and then run it on the same machine as it was packaged, the packaged app can correctly find the SQL Server database that the application was using when it was packaged.  However, when we move the packaged app to a different machine it can't find the same SQL server database even though it is running on the same domain.

We want to be able to distribute the packaged app to desktops outside of our domain and for them to connect to different SQL server databases (preferably using ODBC/DSN connection options).  Is this possible?  If so, how do we do it - do we need the licensed version to complete the evaluation?



__________________


Senior Member

Status: Offline
Posts: 268
Date:
Permalink   
 

The issue shouldn't be with SQL TCP connection, and certainly not with your Cameyo license. It could be that your issue is caused by some intermediate component (ODBC etc) which was installed before you captured your application with Cameyo? If that were the case, then the package wouldn't contain the required component (i.e. ODBC or any underlying configuration) and hence wouldn't be able to connect to the SQL.
Was the machine totally clean before you started the capture, or did it already have some components / configuration on it?

__________________
Page 1 of 1  sorted by
 
Quick Reply

Please log in to post quick replies.



Create your own FREE Forum
Report Abuse
Powered by ActiveBoard