Size of GBPVR.MDB

[ww4397]

Hi,

My gbpvr.mdb is about 186MB. I'm wondering if that is a reasonable size? I'm keeping about 14 days of channel lineups on my system. My gbpvr.old file is about 15MB and I thought that was supposed to be a copy of gbpvr.mdb. Something about the 186MB vs. 15MB seems suspicious to me.

Any thoughts are welcome.

Thanks.

[sub]

Access databases are terrible at becoming huge with lots of unused space. They never reclaim space automatically.

If you hit the OK button in the config app, it'll try to run the included jetcomp utility to compact the database to remove unused space.

[ww4397]

Access databases are terrible at becoming huge with lots of unused space. They never reclaim space automatically.

If you hit the OK button in the config app, it'll try to run the included jetcomp utility to compact the database to remove unused space.

Thanks, Sub. I'll give that a try tonight.

[groover km]

I had a similiar issue not long ago; dunno if it will help, but I posted here...

http://forums.nextpvr.com/showthread.php...=gbpvr.mdb
http://forums.nextpvr.com/showthread.php...=gbpvr.mdb

Might be of interest.

[ww4397]

Thanks, Sub. I'll give that a try tonight.

I tried going into and out of Config, but my gbpvr.mdb size did not change. I did notice a file named compacted.mdb that had the same timestamp as gbpvr.mdb, however. What is compacted.mdb? Is there any other way to get gbpvr.mdb compacted? Can I run Jetcomp.exe directly? Syntax for it?

Thanks.

[sub]

Try manually running jetcomp directly. It'll popup a GUI. You'll need to make sure nothing else has a connection to the database.

[ww4397]

You'll need to make sure nothing else has a connection to the database.

Sorry for such a newbie question, but how do I do that?

[sub]

If you kill any processes with GBPVR in the name, that would be a good start.

[ww4397]

Got an error using Jetcomp. Found someone with Access and Compacted/Repaired there.

File is now less than 10MB and all is well.

[steves]

Sub,

What sort of sizes would you *expect* the database to be.

I keep 14 days of EPG from XMLTV. The XMLTV file is ~8meg but
the access file is 64meg when loaded into a CLEAN/EMPTY database (which started at ~500K)!

Is this normal or is something funny going on?

Background: I have 3 "virtual" tuners (1 x PVR150 but using 3 diff inputs) all using same XMLTV file as source. Approx 30-40 channels in the XMLTV sourced from radiotimes site in UK.

Also is there anyway to automate the database compacting?

Cheers

Steve