Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Database -- Wrong Value Type 3

Status
Not open for further replies.

atlanticdit

IS-IT--Management
Jan 15, 2003
29
US
Been wrapping myself around this issue for a week now. I have a user defined field in the Customer Maintenance screen (7.6.3c on SQL Server 2000) that has a drop down for two values-- Y and N . The max size for that drop down box in the CM screen is 1. The field in the ARCUSFIL_SQL table also has a max size of 1. The field type in the table is char .

The error happens this way:
I go into a customer account and make a selection of either Y or N. Then I hit save and I get the error message. Note that I do not get the error message if I don't change that drop down box but make other changes.

The error message is:

MSL Technical Error Info:

An error occured in MacMSL.dll (ver. 76.300.15.6)
DB Provider Error:
COM Error: Error
Code = 0x800A0D5D
Code meaning = Unknown error 0x800A0D5D
Source = ADODB.Command
Description = Application uses a value of the wrong type for the current operation.
Op : F4, fhRewrite
Table or Script: [servername].[database].DBO.[ARCUSFIL_SQL]

MSL Error Info:
Type: Parameterization Error on CreateParameter.
Function: GetValueString.
Field: USER_DEF_FLD_2
Value: N


I have tried rebooting the SQL server; changing the max size; value type in the SQL table; checked the MDAC versions; removing a piece of code that popped up a message box; etc.

Anyone have experience with this and can shed some light on it. I would much appreciate it.

Thanks,
Dave
 
So I am learning.

And when Exact buys the 3rd party out... Well that's another thread.

I'll stick to finding new ways to get the information out via Crystal Reports.

LOL (That was for Andy)


 
Yea, I know that the 3rd party programmers do those modifications. My rant here as been aimed toward end users.


Andy Baldwin

"Testing is the most overlooked programming language on the books!
 
I know business partners that love modified code and tables. I have a philosophical stand against it. You can add new tables of your own, but thats different.

With Flex, VB, SQL triggers and Event Manager, there isn't much I can think of that would really require modifed code.

To give credit where its due, 2 resellers who have done a good job with modified source code however are Computer Solutions of Monrovia, CA and Alembic of Tempe, AZ.

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

"making predictions is tough, especially about the future" - Yogi Berra
 
This message is for ABaldwin, but I was not sure how to direct it to you. We just upgraded from 7.6.100a to 7.6.300c and are receiving this same MSL error when trying to post POP orders and during the MRP regeneration. I have tried comparing the screen field lengths and types with the MSL tables for IMITMIDX. The differences are on the User Defined fields we have made two of then Integers and shortened all of them from 30. Does changing the screen properties constitute changing the field lengths?

Also, during the regen the table referenced in the error is a work file, so that is why I started with the item master file. Do you have any fast way to find out what the error is?

I am an advanced user who does crystals and event manager events and queries, but am not a programmer. So take it eash on me. :)
 
Janet,

Did you change the field to a integer and shorten then length with screen designer? Or enterprise manager?

The latter constitutes a database change the former is just a screen change.

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

"making predictions is tough, especially about the future" - Yogi Berra
 
With Screen Designer. I will check Enterprise Mgr tomorrow. thanks for the quick reply. Currently we are unable to post production, get errors with IM transactions, and cannot run MRP regen. So we really need to get back on track.
We did have a 3rd party flex app for Taxware that no longer works, and there are fields assigned to taxware, so wonder if that could be the problem? The flex project took away the address push buttons on order entry and replaced them with F8, but this no longer works, so Customer Service and Sales are not to happy. I wonder if we could put the push buttons back for BillTo and ShipTo addresses?

I appreciate any info. thanks.
Janet
 
Janet,

If you or your VAR changed the fields in EM then I think you are in big trouble.

As for your flex issue. It is difficult to say whay your flex is not working not knowing who wrote it, what exactly it does, and what exactly was required to bring it online.

When did it stop working?
When did the posting, IM trans, and MRP stop working?
Were all of these and the flex working at some point in time?

Did they all stop working when this change was made to the fields?

As to putting the push buttons back, well once again see the above questions.

Was this flex app written by your VAR? If so I would suggest calling them ASAP and getting things fixed. If you are not using the flex app any longer I would have them return your system to a "pre-flex" state. In other words get your system back to the way it was before they installed the app.

If your VAR did not do the flex app for you then I would contact whoever did. Something like that would probably be more of a consulting thing than a tek-tips thing.

Thanks


Andy Baldwin

"Testing is the most overlooked programming language on the books!"

Ask a great question, get a great answer. Ask a vague question, get a vague answer.
Find out how to get great answers FAQ219-2884.
 
BTW I think it would be best to start a new thread for the flex issues.

Thanks


Andy Baldwin

"Testing is the most overlooked programming language on the books!"

Ask a great question, get a great answer. Ask a vague question, get a vague answer.
Find out how to get great answers FAQ219-2884.
 
Janet,

Did you simply upgrade versions or did you also upgrade platforms? In other words Pervasive to MS SQL?

There is no way the version only upgrade would get rid of your screens if properly performed. However I can seee this happenning if the upgrade was not done correctly or if you changed platforms.

The platform upgrade by itself, withot upgrading taxware code, could also cause Taxware to fail.

Also please take a look at Wisys' taxsys product as an alternative to taxware. Wisys is Bruce Hollinger's new company. Bruce if you are not aware is the founder of Macola.

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

"making predictions is tough, especially about the future" - Yogi Berra
 
I have seen the MSL error on regen following a 7.6.300C update. From memory the problem was actually with MSSCHFIL. In any case, Exact simply sent me a new MSL and the problem was corrected.

Peter Shirley
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top