Hi,
We are piloting a solution of ThinApp'ing our Access 97 - All is well with ThinApp Access 97 running on its own, we are able to open DB's, run Macro's , printing , edit , Save - no issues... but the problem we discovered is in a scenario where,
Operating system: Windows 7 (64 bit)
All these run in 32 bit process..
1) The front end was written using VB 6
2) VB6 app interacts with a MDB file - no issues
3) There is a piece of reporting code in VB 6 which
- Opens Access ( can see my ThinApp'd Access launching) - this is done via a SHELL command within VB6
- VB6 app then interacts with this instance of ThinApp'd Access by issuing commands like inserting / querying data - not an issue
- It then fires a report which should pick up the default printer and present with Printer Dialogue - Issue lies here - it just doesn't do anything..
- Bear in mind that if I launch ThinApp'd Access 97 on its own - I am able to do what I need to - can see printers - can print....no issues
Suprisingly, this features work if I install Access 97 (not ThinApp'd version) - though my application still interacts with ThinApp'd Access...
Tried all sorts of debugging techniques, like Process Monitor, traces - but no joy..
Would seriously appreciate any help which might help us get over this issue...
Regards,
Nav