Whenever I boot my computer and start Pdox11 I get a Welcome screen which I
tell it I don't want. I also get developer preferences set to Beginner and
I reset it to advanced. In addition, if I create an alias in a session, it
only lasts as long as the session no matter what I save or how I do it
unless I create it directly using BDE (I've been writing in Pdox for 15 or
so years, so I know how to save it correctly within Paradox). As long as I
don't reboot, it holds the settings, but once I reboot it's back to square
one. Any thoughts?

On Feb 1, 5:33 pm, Mousehart <mouseh... (AT) trap (DOT) net> wrote:
I was the dirst one to ask about this issue. Deleting the problem
file didn't work for me so I aaplied another suggestion from the
forum. Try the following code by writing a new script.

method run(var eventInfo Event)

var
stRegMenuKey,stRegNode string
liRootKey longint
endvar


liRootKey = regKeyLocalMachine
stRegMenuKey = "Software\\Microsoft\\Windows\\CurrentVersion\\Run "
stRegNode = "PdxRegCl"


try
deleteRegistryKey(stRegMenuKey,stRegNode,liRootKey )
msginfo("Info","PdxRegCl removed from registry")
onfail
errorshow("deleteRegistryKey ret false-probaly didnt exist")
endtry

Worked for me. I really appreciated it.





endMethod

Another issue I had was file associations.

Additionally, on some of my installations, especially when I had previous
version of pdox on computer,
the file associations became "messed up"
and I had to do some registry work to get them fixed.

Currently, when I search in the registry for "Corel.paradox.shell"
I find it a couple of times in the registry
under some kind of id like :
{D761C5B0-E1D9-11d0-B756-00A0C906BCC5}

There are3 subfolders on this machine I fixed
InProcServer32
ProgId
VersionIndependentProgId

InProcServer32 had 2 items
default was C:\Program Files\Paradox\Programs\Pdxse.dll
ThreadingModel was Apartment
ProgId was Corel.Paradox.Shell.11
Version was Corel.Paradox.Shell

Several months ago,
I had the problem that file associations were not working,
and was able to fix them.
I hunted down the ID in registry,
and one of the values was , what I call in scientific terms,
"gobbledeegook".
Simply removing the bad value from the node fixed the issue.

The above values are what I see now.

I am sorry that I did not document this fix more cleanly,
but if others are having the problem,
hopefully this will help point them to a solution,
and they can post back exactly what they did as permanent record of a fix.

Hope this helps someone else.

Robert Wiltshire