Error Calling External Object Function Open Powerbuilder
Contents |
and SafetyAsset NetworkAsset powerbuilder application execution error (r0035) Operations and MaintenanceCommerceOverviewSubscription Billing and Revenue
Powerbuilder Error 35
ManagementMaster Data Management for CommerceOmnichannel CommerceFinanceOverviewAccounting and Financial CloseCollaborative Finance error calling external object function opendatasource OperationsEnterprise Risk and ComplianceFinancial Planning and AnalysisTreasury and Financial Risk ManagementHuman ResourcesOverviewCore Human Resources and PayrollHuman
Powerbuilder Error Calling External Object Function
Capital AnalyticsTalent ManagementTime and Attendance ManagementManufacturingOverviewManufacturing NetworkManufacturing OperationsResponsive ManufacturingMarketingOverviewMarket with Speed and AgilityUnique Customer ExperiencesReal-Time Customer InsightsR&D/EngineeringOverviewDesign NetworkDesign OrchestrationProject and Portfolio ManagementSalesOverviewCollaborative Quote to CashSales Force AutomationSales Performance ManagementSelling Through Contact CentersServiceOverviewEfficient Field powerbuilder application execution error r0002 Service ManagementOmnichannel Customer ServiceTransparent Service Process and OperationsSourcing and ProcurementOverviewContingent Workforce ManagementDirect ProcurementSelf-Service ProcurementServices ProcurementStrategic Sourcing and Supplier ManagementSupply ChainOverviewDemand ManagementDemand NetworkLogistics NetworkManufacturing Planning and SchedulingResponse NetworkResponse and Supply ManagementSales, Inventory, and Operations PlanningTransportation ManagementWarehouse ManagementSustainabilityOverviewEnvironment, Health, and SafetyProduct Safety and Stewardship NetworkBrowse by IndustryAerospace and DefenseAutomotiveBankingChemicalsConsumer ProductsDefense and SecurityEngineering, Construction, and OperationsHealthcareHigh TechHigher Education and ResearchIndustrial Machinery and ComponentsInsuranceLife SciencesMediaMill ProductsMiningOil and GasProfessional ServicesPublic SectorRetailSports and EntertainmentTelecommunicationsTravel and TransportationUtilitiesWholesale DistributionBrowse Platform and TechnologyAnalyticsOverviewBusiness IntelligencePredictive AnalyticsGovernance, Risk, and ComplianceEnterprise Performance ManagementApplication Platform and InfrastructureOverviewApplication PlatformContent and CollaborationInterface ManagementProcess Management and IntegrationData ManagementOverviewBig Data on HadoopData Warehou
be down. Please try the request again. Your cache administrator is webmaster. Generated Sun, 09 Oct 2016 03:57:35 GMT by s_ac4 (squid/3.5.20)
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn http://stackoverflow.com/questions/9579658/excel-object-saveas-error-happens-when-existing-file-is-open more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, http://pbdj.sys-con.com/node/42285 helping each other. Join them; it only takes a minute: Sign up Excel Object SaveAs, error happens when Existing File is Open up vote 0 down vote favorite Excel_Obj = CREATE OleObject Excel_Obj.ConnectToNewObject( 'excel.application' ) Excel_Obj.Workbooks.Add Excel_Obj.Application.ActiveWorkbook.WorkSheets.Add Excel_Sheet error calling = Excel_Obj.Application.ActiveWorkbook.WorkSheets[1] //EXAMPLE Excel_Sheet.Cells[1,1] = 45 Excel_Obj.Application.ActiveWorkbook.SaveAs(ls_file,56) //csv //where ls_file = the Opened File error happened after / during saveas. try catch throw "error calling external object..in click..line.. saveas.." -- i want to state to the user that the excel file is open therefore cannot be overwritten properly. I used a try catch and throwed a proper message but before the messagebox for the catch event happens, the PB execution error R0035 happens. any solutions or proper error calling external way to know if the excel file is open. excel ms-office ole powerbuilder share|improve this question edited Apr 7 '14 at 19:09 Kara 3,14473147 asked Mar 6 '12 at 7:39 Sid 32711742 add a comment| 5 Answers 5 active oldest votes up vote 0 down vote You might be able to check if the file is open first, have a look at this answer: how to check if file is opened in excel using OLE (leaves excel process open) share|improve this answer answered Mar 6 '12 at 12:47 Colin Pickard 32k869126 i could do those using try catch in Powerbuilder. the true problem relies on the PB Execution Error upon knowing the file is open. not before. i also put it inside try, but the error still popped out. i dont think my users will ignore this,lol –Sid Mar 7 '12 at 1:04 i still need some help on this. I havent figured this out. my users want a perfect excel extract system. Thanks for the answers...! –Sid Mar 8 '12 at 7:12 add a comment| up vote 0 down vote I'd try a PowerScript FileOpen () call with a LockReadWrite! parameter to see if it can be opened, followed immediately by a FileClose () if it was successful. (I think this is a PowerScript-specific variation on the DXL solution Colin linked t
HAT RUBY SAP SEARCH SILVERLIGHT SYMBIAN VIDEO VIRTUALIZATION WEB 2.0 WEBLOGIC WEBSPHERE WIRELESS XML Home Subscribe Advertise Authors Topics Videos Events Webcasts Internet of Things | Cloud | Big Data | DevOps | Containers | Microservices | WebRTC | Java | Linux | Open Stack | Mobile | Security | SDDC PowerBuilder Authors: Chris Pollach, Yeshim Deniz, Jayaram Krishnaswamy, Kevin Benedict, Avi Rosenthal Related Topics: PowerBuilder PowerBuilder: Article PB, OLE and Word OLE automation is a technology by which you can share information and manipulate services By Andrew Mendes Article Rating: Select ratingGive it 1/5Give it 2/5Give it 3/5Give it 4/5Give it 5/5 December 1, 2000 12:00 AM EST Reads: 19,079 Related Print Email Feedback Add This Blog This Oh, no, that dreaded error calling external function is back! Ever get this message while working with OLE (object linking and embedding)? Well, I have, while trying to integrate PB, OLE, and Word 2000. PowerBuilder is the main tool our organization uses to write our "front office" application, and all our marketing material is printed using mail merge with OLE and Microsoft Word 7. We haven't had any problems so far. However, we're in the process of moving to Microsoft Office 2000. One of my tasks was to test if the mail merge worked with Word 2000. To infinity and beyond it didn't work! I kept getting the dreaded message. After many unsuccessful attempts, I searched the Sybase solutions Web site (www.sybase.com/solutions/) for PB, OLE articles. To my surprise, I learned that I wasn't the only developer tearing my hair out - there were others out there in cyberspace. Success strikes! At last I got PB6.5, OLE, and Word 2000 to talk. Many of the Word 2000 object function calls have changed. The intent of this article is to guide you, step-by-step, through the approach I took to get the mail merge working. Understanding OLE OLE automation is a technology by which you can share information and manipulate services (functions, methods, properties) of other applications (e.g., Microsoft Word, Excel, Outlook). While communicating with another application it's essential to know how to access its services and, of course, the correct syntax. Word 2000 uses Visual Basic for Applications (VBA) syntax. Now where can you find the correct VBA functions syntax and, more important, how do you convert it into the correct PB syntax? The answer: using the Word macro editor and the Visual Basic Object Browser. Using the Word Macro Editor Open Word, click Tools on the toolbar, scroll to Macro, then Record New Macro... (see Figure 1). Enter the new macro nam