OHHHHHH, a little dirty now. What's does the big 10 stands for is it the size of the slong that goes down their throat, now that it's stretched out in needs 11 and now a 12 incher. A few more we going to have to dig up john holmes.
OHHHHHH, a little dirty now. What's does the big 10 stands for is it the size of the slong that goes down their throat, now that it's stretched out in needs 11 and now a 12 incher. A few more we going to have to dig up john holmes.
Ah, you KNOW it's all in fun!
They say, the Sparty Statue outside the stadium will drop his helmet (holds it in his hand) when a virgin walks by. It's NEVER hit the ground!
I just "cleaned" my datapage database, I had 7 "finished" parts (jobs) that had 16 database "parts". dumped them, deleted them, dumped the rest of the database, archived the database files, brought over the new, blank file, loaded teh ascii file, now I have a clean database again. Changed the size of the database from 35.8MB to 18.7MB with no gaps in the database. Without dumping the remaining parts, new database and re-loading them, the size of the database would still be 35.8MB. BTW, that 35.8MB is AFTER I deleted the archived "parts" from the database. 17MB of "dead" storage would have been left in the database unless I cleaned it pre my instructions.
I hope this is fixed in the "new" version of Datapage, but I'm not trying it until some of the "things" I've heard about on here are cleaned/fixed up.
After the "purge" and after opening DPEditor & DatapageRT, these are the files for the database:
