I Feel your pain Darren. We went through that mess before getting to where we are now.
Fortunately, we got hooked up with some tech support people that had been around awhile and understood the problem.
We came to Vantage 8 in Beta ll while running a partially implemented Vantage 6. Before taking V8 live (8.00.809c) we must have done 30 to 40 upgrades, data conversions, a handful of clean installs and importing some data in other than approved Epicor methods. Somewhere along the line we picked up a table IMVALRULE that stayed with us up to 8.03.305h. Problem was this table did not do anything until .400. The data conversion was failing for us because it was trying to create this table for .400 but would fail since we already had one. Naturally the table structure was nothing like it needed to be.
Once we deleted the IMVALRULE table from 8.03.305h the conversion ran clean. The other thing they had us do was run a program 803401NullFixer.r that ran through .400 SQL tables reformatting columns that had null values. That was an eye opener. We knew that Vantage did not like null values and were always careful in our work to not create any. This program ran for hours and says it cleaned up thousands of records. From what I could tell we had never done any work where the nulls were found (mostly user definable fields - but not all) and have to believe they were the result of Vantage conversion programs over our V8 life. We are finding 8.03.405a to be far more stable than any previous version we've worked with and believe the null fixer program has much to do with that. I'd recommend it to anyone who has not run it. Now if we can just get the db back down to a decent size we should be in good shape.
David J. Murphy
Information Systems Manager
A&A Machine & Fabrication, LLC
Elevating the Art of precision machining
and fabrication from concept to completion
Voice (409) 938-4274
Fax (409) 938-3925
www.aagroup.com
[Non-text portions of this message have been removed]
Fortunately, we got hooked up with some tech support people that had been around awhile and understood the problem.
We came to Vantage 8 in Beta ll while running a partially implemented Vantage 6. Before taking V8 live (8.00.809c) we must have done 30 to 40 upgrades, data conversions, a handful of clean installs and importing some data in other than approved Epicor methods. Somewhere along the line we picked up a table IMVALRULE that stayed with us up to 8.03.305h. Problem was this table did not do anything until .400. The data conversion was failing for us because it was trying to create this table for .400 but would fail since we already had one. Naturally the table structure was nothing like it needed to be.
Once we deleted the IMVALRULE table from 8.03.305h the conversion ran clean. The other thing they had us do was run a program 803401NullFixer.r that ran through .400 SQL tables reformatting columns that had null values. That was an eye opener. We knew that Vantage did not like null values and were always careful in our work to not create any. This program ran for hours and says it cleaned up thousands of records. From what I could tell we had never done any work where the nulls were found (mostly user definable fields - but not all) and have to believe they were the result of Vantage conversion programs over our V8 life. We are finding 8.03.405a to be far more stable than any previous version we've worked with and believe the null fixer program has much to do with that. I'd recommend it to anyone who has not run it. Now if we can just get the db back down to a decent size we should be in good shape.
David J. Murphy
Information Systems Manager
A&A Machine & Fabrication, LLC
Elevating the Art of precision machining
and fabrication from concept to completion
Voice (409) 938-4274
Fax (409) 938-3925
www.aagroup.com
[Non-text portions of this message have been removed]