Hi Bernie;

  Make sure that your app has write privileges to that folder and that this location is not write protected.

  Have you tried running your PB App as ADMIN?

Regards... Chris

Yes, I have tried running it as admin, and I am not sure why the executable would have any different permissions than the IDE since the are on the same computer saving to the same folder. It is a manually created folder that doesn't have any permission restrictions. It works fine running from the PB IDE, but the executable does not save the datawindow. I don't think that it can be a permission issue since the app is writing a log file to the same folder. The log file gets written when running the executable but the datawindow does not save. That is how I know that the SaveAs method is returning a 1 even though it doesn't save anything. It just doesn't make sense.

Oh, I forgot to mention, I am using PowerBuilder 2019.

Try closing the LOG file before executing the SAVE AS and see if that works.
Sometimes an open file will mark the folder as IN USE, which can interfere with other folder-related operations.


Olan

Based on the variable name, it looks like lds_report is a datastore rather than a datawindow.

When running as an executable, are you sure that it is properly instantiated and contains data?

UPDATE ON MY ISSUE:  It looks like I was focused on the SaveAs, but the problem actually is in the retrieve.  It seems to be failing.  I don't know if this is good news or just different bad news.  Hopefully it is at least helpful in figure out the true underlying problem.

Anyway, I don't think it has anything to do with SQL connection since it runs a previous inline SQL statement just fine before I even set up the datawindow code.  The return code on the retrieve is a -1.  The sqlca does not show any errors, though.  A code snippet is below:

lds_report = create datastore
lds_report.dataobject = ls_reportname
lds_report.SetTransObject(sqlca)
li_ret = lds_report.Retrieve()

Make sure the datawindow was actually included in the executable. If you are not creating a PBD, you will probably need a .PBR file.

UPDATE:  OK, I am making progress on figuring out what the issue is.  I did not consider that fact, that I imported the datawindows from from an older version of PowerBuilder, to be a factor with this issue but it seems to be directly related to the problem.   

Roland Smith's comment about the PBD file made me think that maybe the datawindows were causing the problems.   I decided to create a datawindow from scratch and lo and behold that one worked just fine.  So now I am faced with the mystery of why the older datawindows don't work. It still does not make sense why it works fine in the IDE but not the executable.  Below is what I have found out when running from the executable:

1. An unmodified older datawindow fails on the retrieve.
2. An older datawindow that I opened, modified and saved also fails.
3. Newly created datawindow, successfully retrieves and the saveas also succeeds in saving the file.

Why does it have a problem with the older datawindows that I imported in?

Even opening, modifying and saving the older datawindow in PowerBuilder 2019 doesn't seem to help at all.

Hi Bernie; 

   I suspect that your issue might be corrected as well by editing the DW source and changing the "release" number to "19" &  then save.

Regards ... Chris

Ok....time to start from scratch.

1. In the EXE, is the app connected to the database?
2. If so, does the connected user have READ rights to the database?
3. Is the Retrieve command even getting called?
4. If so, what is the return code?
5. IF an error occurs, are you capturing everything in the DBERROR event?
6. If so, what is th error nessage?


Later -

Olan