EPG Update problems

[stryder]

I am experiencing problems with the EPG update which is a bit confusing.
First of all the size of the database file seems to fluctulate wildly, one day it can be 30 mb , the next day it's 120MB? using Compress and Repair tool in access seems to reduce the size dramatically but the next time an update occurs it starts again.

The other issue I have is performance, the EPG update is taking about 2 hours to run? after a clean EPG it takes about 10 minutes , but seems to gain about 15 minutes a day until it becomes intolerable again.
Is it worth doing a clean EPG before the update each morning?, and if I do how will that affect any recordings that have already been made? will I loose the information from within GBPVR?

Is there someway i can tweak the JET database engine to make it perform better?

I currently use xmltvrtc and grab 14 days worth each morning.
It runs @ 5am in the morning so it is not a huge issue, but obviously it is going to take longer and longer and will require some periodic maintenance to keep the runtime down, it would be nice if I could find a way to do this automatically.
Also worth mentioning is that I have a PVR350 card, and 2 capture sources defined, one for terrestial feed and the other on the s-video in which comes from my NTL cable box.

Do other users experience these problems?
Any help would be appreciated.

Many Thanks!
Stryder

[Major Hostility]

I started using the "complete EPG reload" behavior in the latest release since it dramatically reduces the time it takes to process the update. A 14 day EPG reload from Zap2It now takes less than 5 minutes each morning. It shouldn't cause you to lose any pending recordings, as long as they are still available once the schedule reloads.

On the flip side, this does make the gbpvr.mdb DB grow quite a bit every time it runs, something like about 40MB or so each day for me. For now, I just make sure I run Config.exe every few days which allows the DB to compact itself back down to a nice 5MB.