Initialize IMINVTRX? 1

[crystalreporting]

It's been a long night... Yesterday, we encountered a 132 on a Pervasive file - basically the IMINVTRX table had reached the 4G file limit under the 6.x format. We've tried numerous ways to reduce the file size - SQL statements, Macola's purge function, exporting to text but nothing has worked - Pervasive's monitor shows records being deleted, but they remain after a rebuild. Converting to 7.x now is not an option as this client has huge file sizes (obviously), and rely on Macola every day. Can I simply initialize the IMINVTRX table? Do I only lose my transaction history reports and views? I used the test company to enter OE and POP orders, then initialized the IMINVTRX table - everything still seemed to work OK - anyone ever done this?

Peter Shirley

http://www.linkcorp.com

 

[PhilPPhillips]

If you initialize the table all of the records that are in that table will be gone.

The records are still there after a rebuild because a rebuild just exports the table, re-initializes the table and then reimports the records.

The purge (it takes us forever to run and completely bogs down Macola) should work or better yet a sql statement to delete records should work also.

 

[dgillz]

Why do you say converting to create file version 7x is not an option?

See document 01.193.895 on this issue. There are a few "gotchas" however.

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

http://www.trianglepartners.com

 

[kscheeler]

The IMINVTRX is really just an audit table. You could even turn off items writing to that table with a checkbox on the item master file. You should not have any issues with initializing that file except you won't be able to view or report off any transaction history.

You could copy that file somewhere else, initialize it in their live company and then work on the copy of the table. Either pull out the records as far back as they "need" and then simply append it back into their live table.

Kevin Scheeler

 

[crystalreporting]

Thanks - the 7.x conversion was out of the question due to time constraints - SQL statements (via PCC or ODBC) wouldn't work - editing the text file (with around 2 mil. records) didn't work either. The purge errored out (132 errors as well). We've exported their old IMINVTRX file as well as taken a copy of it, and initialized it. I plan on pulling it all back together when the client in question moves to SQL. The Macola rebuild drops deleted records during the import phase - my understanding has always been that the rebuild is basically an export, initialize and re-import.

Peter Shirley

http://www.linkcorp.com

 

[MacolaHelp]

Did you try ultraedit to text edit the file? It works great to sort by columns (fixed position) in the txt file. Once sorted, I find it easier to copy/paste the records I want to keep into a new file. I've edited files w/several million records, but not one that large physically. I do wonder why the client would want that much data in the iminvtrx. I usually suggest purging this file after a physical count & resetting beginning balances. I find this file most useful to track variances in inventory. Once a physical is done, you should just move forward. If you clear accumulators each period you can use inventory history by period to see summarized usage & it shows trends better than the detail in iminvtrx.

If you think the SQL statements will work to drop records, you could take it to your office, get rid of the data they are willing to let go, export the file, then import append it back into btrieve. When you say they are on 6.x, does that mean 6.15. Yikes! They'd better do something soon.

 

[crystalreporting]

MacolaHelp - someone else mentioned UltraEdit to me as well, so I might try it on the text file to see if it helps - though I have my doubts, as I think any sort of editing application will have problems with the size of the text file itself. 6.x is the file create version under Pervasive 2000i - it's a server configuration option in PCC - with 6.x the physical file size limit is 4G. I hear what you're saying about the number of records and purging.....

Peter Shirley

http://www.linkcorp.com