- Aron Cox
- PowerBuilder
- Thursday, 15 November 2018 05:28 PM UTC
PowerBuilder 2107 R2 1769
Windows 10
Building 32-bit application with PBDs
I've seen this type of issue come up regularly, but I can't find anything that sounds like a solution to my current woes.
Here's what's happening:
Have a 12.5.2 application that was working just fine, we deploy by copying the application, and adding the PBDK files to a folder in the path. We've been doing this for years no problem, including exporting to Excel 12 with SaveAs XLSX!.
We have upgraded to PB2017, and added all the new PBDK files to the same folder as always, including the two required for exporting to Excel:
PBDWExcel12Interop170.dll and Sybase.PowerBuilder.DataWindow.Excel12.dll
However on user PCs the SaveAs XLSX! completely crashes our application, no errors or anything just gone.
If we install the full PowerBuilder Deployment Kit using the MSI file from the PowerBuilder Runtime Packager, then the user starts working again.
Do we need to do something with the two Excel handling dlls other than copy them? I don't remember having to do anything else in the past but perhaps I've forgotten. I've seen mention of the GAC, but I've never had to do that before.
Thank you :)
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.