Dividing a large group into 3 parts

[wapfinator]

Hello, I've been trying to divide a group ("Mygroup") into 3 parts.
Mygroup has 150,000 messages.

This is what I want to end up with:

1. Mgroup           - messages #140,001 - 150,000++
2. Mygroup00-02 - messages #         1 -    70,000
3. Mygroup03-05 - messages # 70,001 - 140,000

As you can see, the first group will have the latest messages. It (and only it) can be updated from PGOffline since it retains the correct group name per Yahoo.  

I am running into errors ("invalid argument") when I try to import messages from #1 into #2 or #3 (after exporting dupes of them out of #1).

Is there a methodical way that this should be done? I have Access 2000 if need be.

[Wilson Logan]

Hi Debbie,

Best thing I think is to create 2 new databases and put your bits of groups individually in a database.

Splitting the group within the same database is doable but is a bad idea. If you want to do it you will need to change the new groupnames directly in the ygroups.mdb database control table. Obviously it won't let you have the same name for a group within the same database as that would mean having the same table names & Access won't allow that.

Cheers,

Wilson.

[wapfinator]

Hi Wilson, Many thanks, I did it.  The group is now in 3 parts within one database.

I made the tablename changes directly via Access. I was emboldened to try it, with the help of this thread: http://pgoffline.com/forum/index.php?board=5;action=display;threadid=455

The "invalid argument" error was occurring because the database was getting too big (temporarily). Compacting the database as I went along fixed that.

Having the 3 parts all together is nice, it makes it possible to search across all of them in one pass.

Splitting the group within the same database is doable but is a bad idea.

Is there a reason to expect problems down the road?  Seems to be working fine so far...

Regards, Debby

[Wilson Logan]

Its only a bad idea if you don't have the techincal knowledge to make the changes directly in Access. The only mistake you can make though, is getting the table & new group names wrong. If you do you'll find out very rapidly.

Cheers,

Wilson.

[wapfinator]

Hmmm... it sounds funny what I wrote. Shoulda said, "Having 3 separate parts all together gives me a choice to search all or only part of a group"

...Yes I'm still stuck w/ my ancient & slow system. Otherwise this wouldn't be an issue!

Well I do appreciate the feedback :-)

Regards, Debby

[Wilson Logan]

Hi Debby,

Hmmm, I'm aware that not being able to limit the search is its biggest shortfall.

I'm getting another developer in May so I'm hoping we can start to address some of the issues that have been building up.

Cheers,

Wilson.

[wapfinator]

Hello Wilson,

That's good to hear!  I hope this means it's thriving in the marketplace as it well deserves to.

Any chance of raising the 2G limit?  (I suspect not, since it must be tied to Access' 2G limit.)

Debby

[Wilson Logan]

Hello Wilson,

>>>> Hi Debby,

That's good to hear!  I hope this means it's thriving in the marketplace as it well deserves to.

>>>> I wish. The other chap got a full time job & has to leave.

Any chance of raising the 2G limit?  (I suspect not, since it must be tied to Access' 2G limit.)

>>>> Its limited by MS Access, not PGO. However... there are plans afoot to make PGO database independant so you can use whatever DB you want (MySQL for exampe).

Cheers,

Wilson.

Debby