[Dxbase] Why to never run DXbase on VISTA/Windows7 in the Program Files directory - wa6axe
Joe WA6AXE
wa6axe at hotmail.com
Tue Nov 1 23:01:49 EDT 2011
HI all!
Well, since I have NEVER run DXbase in the C:\Program Files\ Scientific Solutions\DXbase 2007 directory
on my Windows7 machines -- and, after trying to help Ian (G4GIR) with his setup of DXbase2007 - which WAS
using this old-fashioned DEFAULT directory for the way we installed DXbase on an XP Machine -- I thought
that I wanted to MODIFY my AutoLOTW standalone program to help in these situations -- ONLY to find out
that the old-fashioned DEFAULT directory installation on a VISTA or Windows7 machine is BLOODY TERRIBLE !!
The MANY things that caught my eye on this type of an installation was:
(1) When I imported (Using the DXB Import program) my existing DXbase2007 QSOs into this new Windows7
installation -- instead of just copying over my existing mdb file -- I wanted to SEE what would happen in this
situation to my IMPORTING the QSOs .. of course, I pathed the target mdb file to being my wa6axe.mdb file
that was in the C:\Program Files\ Scientific Solutions\DXbase 2007 directory ----
Well -- $$##$ --- yep - you got it ... the bloody thing imported ALL of the QSOs into that Virtual Store directory's
DXbase2007\wa6axe.mdb file .... and did NOT even send ONE qso into the TARGET mdb file ...
(2) Brought up DXbase2007 from the DEFAULT directory and of course selected the wa6axe.mdb file in THAT
default directory .. Then, when I entered by hand a dummy qso into this logbook .. I closed out DXbase and
looked at the mdb file that was in the default - yep - the one qso (hand poked) is there - no problem ... BUT,
NOTHING of that hand-entered QSO in the Virtual Store mdb file ...
(3) Made an adi file from my newest T32C entries (that were on my XP machine) --- and wanted to see
where THEY would end up - when I did a Non-DXB Import of these 6 QSOs in my DXbase2007 on my
Windows7 machine --- YEP - you guessed it --- ONLY imported into the Virtual Store directory's wa6axe.mdb
file ... not a T32C qso entered into my default directory logbook ....
SO -- I have shown myself that it is ABSOLUTELY impossible to make a BETTER AutoLOTW exe file for the
above situations -- seeing as how YOU will NEVER have ALL of your QSOs in "One Place" !!!!!
The ONLY WAY that the default directory installation would be usable -- and I still would never do it!! ---
is -- IF you always PATH yourself (the program you are using - whether it be DXbase itself -- or one of the
import programs, etc) "always" to use the Virtual Store logbook mdb file .... and, the bummer here is that
NO ONE will ALWAYS remember to path to the Virtual Store mdb file !!!!!!!
If anyone is running DXbase on a VISTA or WINDOWS7 machine -- and you are running it in the
C:\Program Files\ Scientific Solutions\DXbase 2007
default installation directory (the old defaultdirectory) -- then you are in my prayers ... My wife's 25 pistol
can do better at my brain than trying to work-around this type of an installation's effect on my brain ... and,
there ain't much left anyway!!! lol!!
BOTTOMLINE -- NEVER try to use my AutoLOTW program - if you have this default type of install on a
VISTA or WINDOWS7 machine ... it will NOT WORK!!!!
Try comparing your logbook mdb file that is in your default directory against the one that is in the
Virtual Store area --- make you a bet you are missing QSOs ...
Never again!!
Joe wa6axe
More information about the Dxbase
mailing list