Hello everybody,
following situation: I have MS Office 2010 SP1 natively installed on master image which is provisioned as linked clones. Additionally I add MS Access 2010 as ThinApp (packaged with ThinApp v.4.7).
When I try to select ODBC connections via "External Data" -> "ODBC Database" the standard connections like "dBASE Files", "Excel Files", "MS Access Database" do not show up.
While building the application on a clean machine .NET Framework is already installed as suggested by VMware for ThinApp'ing MS Office 2010.
These lines are added to Package.ini before build process is started to make communication between native install and ThinApp possible:
VirtualizeExternalOutOfProcessCOM=0
ChildProcessEnvironmentExceptions=WINWORD.EXE;EXCEL.EXE;POWERPNT.EXE; OUTLOOK.EXE;MOC:EXE;NOTES.EXE
ChildProcessEnvironmentDefault=Virtual
Any help would be appreciated
Well, they are not supposed to show up in the "File Data Source" tab. They are present in the "Machine Data Source" tab.
Your virtual MS Access seems to work fine to me. To confirm that you can try to create a new file or machine data source.
Well, they are not supposed to show up in the "File Data Source" tab. They are present in the "Machine Data Source" tab.
Your virtual MS Access seems to work fine to me. To confirm that you can try to create a new file or machine data source.
Hello OliAH,
you're right! ODBC connections only show up in Machine Data Source and they also do in my ThinApp!
Maybe my ThinApp is working properly, but I still face problems with an .adp-Database. The Database is annoying me with the setup routine for MS Office 2010 starting up after logging on to the database. I have been able to prevent this in the past by putting an old mscomctl.ocx into the folder %SystemSystem% and de- and reregister the mscomctl.ocx on the master. But after changes on the master this behavour is back, even after de- and reregistering the Activex component mscomctl.ocx.
Think I'll have to open up a new post for this.
Thanks a lot!
