Last night I followed the instructions on fixing a group format error on the !data file. I cleared the table, removed the indexes, and then recreated the indexes. This worked great on my development system it's now clean and pretty. Unfortunately, on the live system it was a no go. I did this procedure 3 times and the verify still found the GFE error.

The GFE is !data Group 0 Code 3 Initial setup failed. Primary header type 32 is incorrect.

1. In my memory I remember something about not being able to run caching with Arev because of problems????

Interesting side effects I have noticed: I use to be able start up

arev from a command prompt now sometimes when I do this expanded

memory is not active. It doesn't happen reliably to diagnose why.

We are running Arev now with the Universal driver on Microsoft 2003

Server

Does anybody have a direction I can go??? Any ideas?

It sounds as though you are trying to verify a UD3 file (which has a changed header structure) with AREV (whose verify routine don't understand the changed header structure).

For a Q&D just LIST ONLY FILE (N and see if it gets through without GFEs :)

[email protected]

The Sprezzatura Group Web Site

World Leaders in all things RevSoft

Thank-you

View this thread on the forum...