I have a problem with the 11270 error that I have fought for years. When it goes away, I silently celebrate the success because I have no idea why it was fixed. Now, the problem seems to stay more often. I have a Paradox database on PC1, where it is primarily used. PC2 is typically the only other one that accesses this database, however, others do at times. PC2 runs an access database that has tables that pull the paradox data in and uses it in an access report. I have recently updated PC2 to a Windows 7 system with Office 2010. Office 2010 could not talk at all to Paradox so I re-loaded access 2003 for this one purpose. More often than not, I get the 11270 error when trying to access that other computer. Sometimes the following things work: rebooting PC1, finding and deleting the *.lck files on PC1, accessing it first thing in the morning before anyone uses PC1 (even without a fresh boot). Lately there seems to be nothing I can do to fix the problem. Any ideas where I can go from here?
that particular error message isn't familiar, but the overall scenario is.. you're trying to concurrently use access with paradox, which will almost always result in problems.. access doesn't use the bde directly, so it does not share and manage files the same way..
yes, the office 2010 issue makes sense, because office 2010 no longer pretends to support paradox.. yes, the lock file and reboot errors make sense, because of what I said above.. you have options, you just need to pick the one(s) that work for you:
use access with the paradox data only when nobody is using paradox
use access on a copy of the paradox data
export text files from paradox that access can work with, instead
Steven Green - Myrtle Beach, South Carolina USA