|
They are coming in from web by a call from a Visual Basic program. I tried to update the program and use a Procedure Interface, and saw the problem with it.So I reverted to the original *Entry Plist.
HOW are you calling it from Visual Basic? As a stored procedure?If so, does the stored prcoedure definition (from CREATE PROCEDURE) match the parameter list in your program?
This sort of problem is caused by using unmatched parameters. The caller is (somehow) specifying different lengths or data types for at least one of the parameters. Without any clue of how you're calling the program, there's very little we can do to help you, other than say "make sure the parameters match."
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
