attempting to lock problem in VFP 6 in windows 7 64 bit

Question

Hi

I have a peculiar problem with my new win 7 64 bit clients.

Our vfp 6 applications work fine in win 7 32 bit, however when running the apps in W7 64 bit clients, we have this issue - 

The system message 'Attempting to lock.. press ESC to cancel' appears invariably while trying to open vfp database and associated tables and views.

The above message appears in clients (irrespective of their o/s) trying to run the application subsequently after a W7 64 bit client successfully opens the form (database/tables/views).

Checked the codes and added all file opening routines to open files in shared mode, set exclusive off etc.

However, the problem remains. If a w7 64 bit client is the first to open the vfp object, subsequent clients get this message.

What could possibly be the solution to this?

Our network o/s is Netware 6.5

Thank you all in advance.

Regds

Remsang

 

 

Answer 1

This is known problem between W7 and Novell. System simply does not release locks placed during DBF file opening...

Solution which worked in one case was:

Uninstall the Win 7 Novell Client altogether, including all traces of NMAS and NICI

Download and install "Novell Client 2 for Windows Vista-2008"
Choose the Custom Setup and DESELECT NMAS

You could also check if some newer version of W7 Novell Client exists as the first step before uninstallation.

 

Answer 2

NMAS, NICI removed at client and Client file caching and  level 2 oplocks off (disabled) in server.

Still the same problem.

Also tested further and noticed that the above locking problem occurs only for local views.

Opening of tables in w7 64 bit works fine.

 

Answer 3

So, I have to say I don't know the answer and I cannot test this error in my envirionment. Sorry.

Possible work around:

Wievs are defined in database and it is possible the lock is placed on the database record only. Database is obviously not updated by VFP application, so you could try to use local database at each workstation.

Answer 4

Turn off SMB2 on client and server to solve.