[Dxbase] DXB 2K7 and Windows 7/64 Head Aches

Sat Nov 6 14:35:01 EDT 2010

I am continuing to have nuisance problems with DXBase 2007 installed on my 
Windows 7 PC. The latest problem is that when I went to print QSL labels 
the program used AA4LU for "mycall" despite the fact that the call sign in 
the Select Label Type window and user seetings correctly showed my call as 
AA1QD. Along with all of the other nuisance problems, like some window 
column widths not being remembered and the default QSL via in the log being 
wrong (set correctly in user options) it’s quite aggravating. I ended up 
editing the label file to hard code my callsign and had to reprint a big 
batch of labels. When I make changes in DXBase it appears that the 
DXB2007.INI file is being updated but from what I've read I'm thinking that 
when DXbase is starting up the operating system seems to be forcing it to 
use registry entries rather than INI file info and the registry entries 
apparently aren't getting updated. I thought that maybe running DXbase "as 
administrator" might solve the problems but it doesn't. Also trying various 
"compatibility" modes to run it doesn't seem to help either.
Can anyone help me understand better what Windows 7 really does wrt the INI 
file info. If I have to go in to edit the registry I can do that but would 
rather not risk it.
Hopefully the new version of DXBase that Santa brings will solve all these 
problems. I really like Dxbase and don't want to have to go through the 
learning curve of new software and end up using another program that I like 
less than Dxbase.
tnx
Dale, AA1QD