We use remote procedure calls all over our application. All of them are defined in n_tr.
When we designed this section of the application, it was back when we were using ASA6. Calls worked flawlessly.
Now we've moved up to SQL Anywhere 12. Been there for some time. Then I get the call that this particular module isn't working correctly.
I start digging through the code and notice that certain aspects of what is supposed to be handled through the stored procedure isn't happening.
So I put a simple print statement in the stored procedure. Ran this module again. Statement never printed. Hmmmm.
Let me try the debugger. So I put some debugger stops in this stored procedure over in SQL Anywhere. Ran it for all connections. Figured that it would fire the procedure, and since I'm testing locally on my machine, it would stop at the point it hit the first debug point and the application would wait for me to step though the procedure, then hand control back to the application.
But again. Nothing. It's like it gets to that call, and just steps past it.
I read that since the RPC doesn't return any arguments, to set it up as a subroutine. It had been set up as a function. So I converted the RPC call to a Subroutine. Ran it again. Absolutely nothing. Gets to the call, and just keeps on going. Doesn't stop at any of the debug points and never hits the print statement.
And for the record, There are other RPC's that are firing just fine. We have one specially that fires when you switch the project you're in. That way it sets up all the connection level variables on each project.
Does anybody have any thoughts on what else I might look at that could be causing this? Just find it strange that this was working just fine, and now under SQL Anywhere 12 it just seems like it is silently failing.
Any ideas on this would be greatly appreciated.
TIA for everyone's help!!
Jeff Gibson
Intercept Solutions
Nashville, TN