Windows 10 Posts

We have  been running Paradox 11 on Windows 7 for awhile. We have bought new Windows 10 pc‘s and are going through the configuration process. We have a Konica C658 printer. We are running into an issue where Paradox will not pick up the default printer preferences. For example, in the printer driver we have set Paper size = 14.5 x 11 Orientation = Portrait Print Type = 1-Sided Staple = Left Corner But when you print from Paradox, for example instead of Print Type = 1-Sided, we are getting 2-Sided. I know I can set some of these settings via code(I don‘t believe I can set it to staple). But I‘d rather not go back and change this on every form where I print reports. Has anyone run into issues with Paradox not picking up the printer preferences that are set on the printer driver? Oall other apps, such as the Microsoft Office apps, work fine. Thanks, Gary

Posted to MB Topic: Paradox Setup, Vista, etc. « Paradox Board

{Too Long!}

Posted to MB Topic: Paradox Forms « Paradox Board

{Too Long!}

Posted to MB Topic: Paradox Tables « Paradox Board

Hi all, I have run Paradox 8 on a Server 2003 for over a decade using RDP sessions with dozens of users.  I upgraded to Paradox 11 and Windows 10 clients.  All still fine.  This week, though, I migrated my database from a Server 2003 to a Server 2016.  All programs run fine but I am getting multiple index out of dates each day when multiple users save data in the tables.  So far, I have: 1.  Disabled write cache on drives 2.  Excluded database directories and c:\netdir directory from Windows Defender scanning 3.  Edited LanmanServer and LanmanWorkstation to add keys 'enableoplocks'=0 and 'disableoplocks'=1 4.  Local share on BDE=true 5.  All sessions map to the same c:\netdir for control file and use same path to database tables Any help from those who have succeeded with a Server 2016 hosting tables in an RDS environment would be greatly appreciated.  

Posted to MB Topic: Paradox Setup, Vista, etc. « Paradox Board

We have almost completed our port from Windows 7 and Paradox 8 to Windows 10 and Paradox 11.  I am down to the last few bugs.  One is that all my date queries suddenly produce no results.  It turns out this is because I had been using 4-digit years, and now only 2-digit years seem to work in queries althought years are displayed as 4-digit in the queried table.  Weird. Anyhow, I suppose I could reprogram all date queries as 2-digit years, but this seem like bad practice.  And hard. So, I wondered if there is anywhere that I can easily reset the date format back to 4-digit years?  I already tried the Windows 10 short format, but it was already set to 4-digit years.  Any other ideas? Thanks! Steve

Posted to MB Topic: ObjectPAL « Paradox Board