• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • GetOpenFileName not working in .NET deployed PB program / browser

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (5)

Resolved GetOpenFileName not working in .NET deployed PB program / browser

  1. Advice
0
Votes
Undo
  1. Murugeshan KN
    Murugeshan KN
  2. PowerBuilder
  3. Saturday, 9 November 2019 11:46 AM UTC

GetOpenFileName function works normal in the regular windows app and same thing when deployed in .net version it is not prompting the Open Dialog window.  Please suggest some solution.

WS check
Populate Fields (not Bookmarks) in a WORD OLE
Accepted Answer
Kai Zhao @Appeon
Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Monday, 11 November 2019 07:14 AM UTC
  2. PowerBuilder
  3. # Permalink

Hi Murugeshan,

The function GetOpenFileName is supported by PowerServer Web but unsupported by PowerServer Mobile. If you want to run application on web only, please make sure the project type is ‘Web’ (Toolkit > Configure > Application Profile Configuration> Basic Settings), thus the unsupported features report would only include the unsupported features by PowerServer Web (the report will include all the unsupported features by Web and Mobile if the project type is ‘Both’).

Regards,
ZhaoKai

Attachments (1)
ProductType.png ProductType.png
Comment
There are no comments made yet.
Responses (5)
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Saturday, 9 November 2019 16:35 PM UTC
  2. PowerBuilder
  3. # 1

When you say .NET and browser are you talking about PowerBuilder WebForms or PowerServer?

Comment
There are no comments made yet.
Murugeshan KN
Murugeshan KN Accepted Answer Pending Moderation
  1. Sunday, 10 November 2019 05:07 AM UTC
  2. PowerBuilder
  3. # 2

Absolutely Yes.

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Sunday, 10 November 2019 06:17 AM UTC
Which one? I listed two things. We can't help you if you don't explain clearly.
  1. Helpful
Murugeshan KN
  1. Murugeshan KN
  2. Sunday, 10 November 2019 06:40 AM UTC
Sorry. It is on Powerserver. Please help me. I am totally stuck at this point.

  1. Helpful
There are no comments made yet.
Murugeshan KN
Murugeshan KN Accepted Answer Pending Moderation
  1. Monday, 11 November 2019 08:43 AM UTC
  2. PowerBuilder
  3. # 3

Hi ZhaoKai,

You solved my problem.

Earlier I maintained Project Type as 'Both' and while deploying to Power Server, no report of Unsupported features were listed and it was not working too.

Now as per your suggestion I maintained Project Type as 'Web' and it started working.

Thanks you very much. 

Best Regards

Murugeshan KN

 

 

 

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 11 November 2019 16:02 PM UTC
  2. PowerBuilder
  3. # 4

Hi Murugeshan;

  FWIW: I always create two PowerServer profiles per Application. One for Web and the other for Mobile. There are a few subtle differences between the environments. Having one profile for each type of deployment allows me to keep these differences separated (by different PBL libraries) and the PS Toolkit generating the appropriate code and/or warning messages.

  Its a bit of a PIA to have both PS Toolkit profiles but it pays off in the long run IMHO. Just my $0.02.

Regards ... Chris

Comment
Murugeshan KN
  1. Murugeshan KN
  2. Tuesday, 12 November 2019 12:37 PM UTC
I welcome your suggestion. Thank you.
  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.