We recently converted a client from 2.01b Standard to Navion 2009 SQL. The client's application, in 2.01b was modified to process credit card using the the xAuthorize dll. All the modifided objects were deployed to the 2009 applicartion as they existed in the 2.01b database (no changes were made).
When the users try to process a credit card in the 2009 application the system returns an error message that indicate that the credit card was declined (Return Code 2 from the xAuthorized dll).
I saw where this happened to other users back in 2008/209. Did anyone resolved this issue or found the cause of the issue that did not involve re-writing the entire application?
0
Comments
What does that mean?
That's what I thought you meant, I just found it a bit hard to believe. [-o<
When you upgrade you need to take the changes from your old objects and integrate them into the new objects. You simply can't do it the way you did. Find who ever did your upgrade, and after you shoot them, talk with the replacement developer and discuss about how to fix it.
If you know it so well, then why are you only giving this very basic information?
First of all show us the object ID's you pulled into 2009 for this modification, are any native objects involved?
If not, have you upgraded the 2.01 code to 2009 standards? Things have changed you know...
Also what version of 2009 did you upgrade to? Have you run the date correction?
Have you verified the data upgrade went correctly?
What have you tried to come to this conclusion? Please post the findings of your testing, that might help?
Funny, I needed that
RIS Plus, LLC