Hi, Langley!
 LM> Its good to see that someone else is having to make the jump from 4.5 to
 LM> PDOX for windoze.  I have just recently loaded it into my machine and 
   Misery loves company?  
 LM> have just barely played with it.  Tell me, is the video any help (I have 
 LM> not reviewed it, though it came with the software)?  
   I have 2 videos.  One for the basic stuff, most of which I figured out by 
myself just playing with it, although there were a few good tips.  The other 
is the ObjectPAL video, but I haven't finished the tutorial in the manual 
yet, 
so I'm holding off on that.  (I don't have much time to play around with new 
software.  They hired me to do locksmithing and handle all the emergencies 
around here, so my computer time is mostly spent keeping track of what I did 
or planning what to do next.  Last month I got about 4 hours to learn about 
ObjectPAL, so it's slow going.)
 LM> Also, any hints or correlations between the two versions you notice will 
 LM> be appreciated.  
   Okay.  The main thing I noticed is that Paradox for Windows has a major 
problem trying to read a table if it has a lookup table in another directory, 
and will not read it at all if that Table Lookup was set up in Paradox for 
DOS.  (The DOS version doesn't usually keep track of tables with the full 
path 
name, while the Windows version absolutely requires a full path name.)
   So, the simplest thing is to keep all your tables together in the same 
directory.  The next simplest solution is to ONLY use PdoxWin to create 
lookup 
table links.  The really complicated solution is to first change to a 
different, non-Paradox subdirectory on the same drive in the DOS version, 
then 
change to a subdirectory on a different drive, and only then use View to get 
the table on screen, clear all the Lookups for all the fields and recreate 
them from that far distant subdirectory.  Of course the lookup tables must 
also have any lookups set up as above, too.
   I ended up using queries to make vanilla copies of all my tables, copying 
them to another subdirectory so I could use the original names, and then 
using 
the Windows version to restructure them all, wishing I had some crossover 
product that could cut complicated Picture strings from the DOS table and 
paste them in the Windows version.  (Know of any?)
   What else?  I had high hopes for the object converters, but had nothing 
but 
trouble with them (probably due to the above mentioned table lookup problem.) 
I found that the Windows forms generator was so easy to use that I simply 
created new ones in half the time it took to try to modify one of the 
converted DOS forms.  (Hint: don't try to use any of the automated forms.  
Choose Blank form and put the fields you want where you want them.  Get to 
know how to use Snap to Grid, and Align, and the neat way that you can 
combine 
active fields in a text box to concatenate data.)
   I like my forms to do my reporting for me on the fly by showing everything 
at once, so I have one form which shows a door and all the info about it from 
the Doors table, linked through the Doorkey and Groups tables to show all the 
keys that will work in it and all the info about each from the Keys table, 
which is in turn linked through the WhoKey table to the Employee table to 
show 
all the people who have each key (as I click on each one) and where they can 
be reached.  That's something the DOS version could only do with a lot of 
denormalized data and a consequent large amount of maintenance to keep it 
accurate.  In the Windows version, I can look up someone's phone number and 
edit it on screen by using Zoom to find one of the doors he can get into!
   I'm working on trying to create a button that will enable me to have the 
computer's modem dial that phone number.  I'll post it here when I figure it 
out.
 LM> We have not committed to the windoze version yet 
   Neither have we.
 LM> (in fact I am still developing applications in 4.5 daily), 
   I'm still coming up with improvements for my DOS application, too.
 LM> but I think it is inevitable.  
   (sigh) Me too.
 LM>
   Say, you and I have the same initials.  That could cause problems if you 
try to answer me and quote both of us, so use lower case lm> to quote my 
portions if you respond to this. 
   -- Lee --
... When in doubt, you're probably unsure about something.
--- Via Silver Xpress V3.02
---------------