This is what I do as well. You did not specify this, but I think you mean that you are opening the DB remotely from FM Go so you can see changes made by FM Advance as they are made. This works well for me.
Overall, scripts do not acts differently on GO vs. FM Pro, so I am spend my time debugging the Pro app and testing layouts etc on GO.
Yes, I remotely open my DB from the Laptop.
It is time consuming debuging, as I have to just run the iPad solution and try and capture (in my head) any breaks or errors.
I keep thinking I should design the scripts differently - but not sure how!!!!!!
The errors should be no different than when it is running on FM Advance, so you can step thru the code with the debugger on your development machine. You shouldn't need (except on rare occasion) a debugger on the FM Go side.
If I am having difficulty on the GO side, I sometimes add a Custom Dialog to the script to pop up when it gets somewhere so I can check the value of a variable etc. on the iPad, but generally I can just debug on my Mac and it works on FM GO. Historically, I have only needed to do this when dealing with variables that involve the file system (Get (TemporaryPath) etc) as GO handles things a wee bit differently than a PC or Mac.
There are three real sets of difference that you need to handle.
1. Some script steps are not available in iOS. You can check for these easily using fmpro. Use the pop-up selector at the lower left hand corner of the script maker dialog.
2. User input objects are different on iOS and the desktop. You'll need to interact with all the layouts on the device to see what they do.
3. User expectations/behaviour are very different. If you can't use the app when you are "tired and emotional" go back to the drawing board.