AS and FMPA runtime fail on build

Question

OK I have one that doesn't seem to be answered. I'll past the whole script

The problem is with the TRY. Since it is happening in the Finder and I am trying to pass some info back to FM. THis works fine as a FM script but fails in the runtime. As far as I can tell the only solution would be to change all the Filemaker Pro Advanced references to the runtime app BUT I can't do that because FMPA wants me to show it the app and of course it isn't built yet! So I guess I could build the runtime and then edit IT'S scripts to work. But that seems like a funky workaround. I tried using "me" but I think because it's part of a try still running in the Finder it fails.

-- script to copy files to PT directory 1/21/02

set copysounds to ""  
set thetarget to ""  
set x to ""  
set filename to ""  
tell application "FileMaker Pro Advanced"  
--activate  
 set recordCount to count of records  
end tell  
choose folder with prompt "Pick a destination folder"  
set thetarget to result  
repeat with x from 1 to recordCount  
tell application "FileMaker Pro Advanced"  
  set copysounds to cell "Find Path" of record x  
  set effectName to cell "Effect Name:" of record x  
  set filename to ((thetarget as text) & (cell "Effect Name:" of record x))  
  set cell "error flag" of record x to ""  
  set notFoundError to ""  
  set DupOK to ""  
  -- find out if file esists  
  tell application "Finder"  
   activate  
   try  
    alias copysounds  
   on error  
    set notFoundError to "true"  
    display dialog effectName & "  file was not found.  Check     Path." buttons {"OK"} default button 1 with icon stop  
   tell application "FileMaker Pro Advanced"  
     set cell "error flag" of record x to "Path Invalid"  
    end tell  
    --return  
   end try  

Answer 1

Not having a copy of the database makes it hard for me to test but lets start here. You have allot of things out of place so I fixed up your code

try this

  -- script to copy files to PT directory 1/21/02

  set copysounds to ""
  set thetarget to ""
  set x to ""
  set filename to ""
  set thetarget to choose folder with prompt "Pick a destination folder"
  tell application "FileMaker Pro 10"
    set recordCount to count of records
    repeat with x from 1 to recordCount
        set copysounds to cell "Find Path" of record x
        set effectName to cell "Effect Name:" of record x
        set filename to ((thetarget as text) & (cell "Effect Name:" of record x))
        set cell "error flag" of record x to ""
        set notFoundError to ""
        set DupOK to ""
        try
            tell application "Finder" to alias copysounds
        on error
            set notFoundError to "true"
            display dialog effectName & "  file was not found.  Check     Path." buttons {"OK"} default button 1 with icon stop
            set cell "error flag" of record x to "Path Invalid"
        end try
    end repeat
  end tell

Answer 2

UPDATE: Pardon a simple question, but do you have the database open when you run the script as an application or otherwise. The only way I can get the same "object not found" error in Applescript is if I don't have database open. See the following example...

tell application "FileMaker Pro"
    set theRecords to records --> if a database isn't open in Filemaker, this gets an "object not found" error.
    return theRecords --> if a database is open, a list of records is returned.

end tell

I can't help but think that something more fundamental than runtimes is being missed here.

---

As far as I can tell the only solution would be to change all the Filemaker Pro Advanced references to the runtime app BUT I can't do that because FMPA wants me to show it the app and of course it isn't built yet! So I guess I could build the runtime and then edit IT'S scripts to work. But that seems like a funky workaround.

You can save the script as an application and save it so that you can edit it in the Script Editor application. I've done this numerous times before. For debugging, instead of going to the activity viewer, you can write to a file instead and read that when the script is done doing its thing. It's funky but not out of the ordinary for Applescript.

I tried using "me" but I think because it's part of a try still running in the Finder it fails.

mcgrailm's code is much cleaner, but it seems to me you're still going to get an error on the try regardless if you use me or not; trying to get the alias of a file will return an error if the path is incorrect every single time. If the error is here...

 try
    tell application "Finder" to alias copysounds
 on error

...then you need to investigate the value copysounds and how that value is generated. I agree with mcgrailm that sample data from your FM DB would be really helpful here, and so would the exact errors you are getting from the try. Something like this will help capture that...

try
    -- insert actions here
on error the error_message number the error_number
    -- do something with the strings error_message and error_number
end try