I've never used the application portion (I prefer to just have an external form as a Main Menu) maybe just create an external test form and plop that run code into a bit button eep to test it. If it works then you can narrow down the issue to it's something with the code and the app.rba file combo, else try copying the code directly into that bit button eep and figure out if it is an issue with calling the RMD file... ----- Original Message ----- From: Ed Rivkin To: RBASE-L Mailing List Sent: Tuesday, May 18, 2010 1:31 PM Subject: [RBASE-L] - Re: Macro works from R> Prompt; fails when called from.RBA
Rachel, You have the scenario. Run.CFOLOAD.RMD from R> works fine. I am using a xxxx.RBA file for the application and added an action to it to run this macro. When the user clicks on the menu option that runs the macro, it get the error specified below (with Set Error Message On) I am running 7.6. Haven't looked at the temp file data but will do so later today. Thanks for the suggestion. Ed May 18, 2010 11:00:02 AM, [email protected] wrote: please clarify.. so in the r>prompt you type Run CFOLOAD.RMD and it works? but when you (click a button or what does a user do to start running the code) it fails even though everything is the same (data and file)? what version are you using? did you look at the data in the temp table after it is run? ----- Original Message ----- From: Ed Rivkin To: RBASE-L Mailing List Sent: Tuesday, May 18, 2010 10:28 AM Subject: [RBASE-L] - Macro works from R> Prompt; fails when called from .RBA Hi folks, I am scratching my head on this one. I wrote a macro (CFOLOAD.rmd) to create a table, do some calculations, and print a report. The macro works fine when run from the R> prompt. The report is produced with the expected results. I have also run the macro using Trace and found no errors except one "No Rows Exist or Satisfy Specific Clause" message towards the end of the macro. I added an action to my existing .RBA application to run the macro. The Action is Run CFOLOAD.RMD Return as a custom action. The action fails. I added Set Message On and Set Error Message On to the macro and reran it from the .RBA. It now fails with five: "No Rows Exist or Satisfy Specific Clause (2059) Any thoughts or suggestions would be appreciated. Cheers, Ed
