Sandy, Compacting the mdb file with the standard way (Access 97 or Access Maintainer) does NOT remove any valid data.. The best way to compact our mdb file(s) is by using the standard method.
73 Joe wa6axe Sanford Ardern wrote: > > Subject: Re: Re:[Dxbase] Database size > > >> Joe >> OOPS!! There is one problem doing it this way that I had noticed >> before but forgot. You lose your 'Callsign Notes' in the summary >> window. Do you know if this normally happens when you shrink the .mdb >> file using the other methods? >> Sandy W4DUP >> >> ----- Original Message ----- From: "Sanford Ardern" >> <[EMAIL PROTECTED]> >> To: "Joseph Glockner" <[EMAIL PROTECTED]>; "DXbase Reflector" >> <[email protected]> >> Sent: Tuesday, October 12, 2004 9:29 PM >> Subject: Re:[Dxbase] Database size >> >> >>> Joe >>> Going on the logic of doing ADIF imports into DXB2005 I have >>> EXPORTED my W4DUP.mdb as >>> ADIF from my log program as W4DUP2.adi. Then IMPORTED the .adi file >>> back as W4DUP2.MDB and the size shrinks from 106038 KB to 15126 KB - >>> about a 7 to 1 ratio. In other words to me it looks like the exact >>> same thing as IMPORTING from the old DXbase 5.0 (ADIF). The two >>> logs - W4DUP.mdb and W4DUP2.mdb are identical, including Notes etc >>> as far as I can tell. Is there a reason not to shrink the .mdb this >>> way? Maybe there's something I'm not thinking of but it seems to be >>> giving a perfect import every time. >>> Off the subject but---- I got my Address Bar back in XP. Found >>> out that it's a common problem. >>> >>> Sandy W4DUP >>> ______________________________________________________________ >>> Dxbase mailing list >>> Home: http://mailman.qth.net/mailman/listinfo/dxbase >>> Help: http://mailman.qth.net/mmfaq.htm >>> Post: mailto:[email protected] >>> >> > >
