mse3000 Posted March 13, 2012 Share Posted March 13, 2012 Is there a known bug in DAQ Factory that stops the graph export function working in Windows 7? The print / export graph funtion works fine in XP and Vista but when exporting a graph and clicking on "browse" to select a file destination, DAQ Factory locks up in 7. Regards, Mark Quote Link to comment Share on other sites More sharing options...
AzeoTech Posted March 13, 2012 Share Posted March 13, 2012 Yes, and I believe it is mentioned somewhere else on this forum (but I can understand not being able to find the post among all the rest). Alas, this is due to a rather old graphing control that we do not have source for. We will be updating the graph in coming releases, which will resolve this, among other things. In the meantime, consider using the page.capture() or the page.printPDF() functions. Quote Link to comment Share on other sites More sharing options...
orlee Posted July 4, 2019 Share Posted July 4, 2019 Hi, I just noted to have the application wipe out (crash and close) on a client PC at the moment we press the "Browse" file select button. Can you suggest a fix? Thanks Quote Link to comment Share on other sites More sharing options...
orlee Posted July 4, 2019 Share Posted July 4, 2019 Forgot to mention: Windows 7 pro, 32 bits Quote Link to comment Share on other sites More sharing options...
AzeoTech Posted July 8, 2019 Share Posted July 8, 2019 Yes, that is the bug mentioned in the post. You can't use the right-click graph capture feature in newer OS's. You'll have to use an alternative such as the printPDF function. Quote Link to comment Share on other sites More sharing options...
kanber Posted January 23, 2020 Share Posted January 23, 2020 Hi, On verison 18.1 when I add a button and set action to Print Settings, if I click button page is changing to blank white page. page.strCurrentPage variable showing null. How can I solve the problem? Quote Link to comment Share on other sites More sharing options...
AzeoTech Posted January 30, 2020 Share Posted January 30, 2020 Try using Page.printSetup() function in a quick sequence instead. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.