Article ID 2362
Article Title INFO: Running a program from the Studio (F5) always compiles, even when not needed
Article URL http://www.dataaccess.com/kbasepublic/KBPrint.asp?ArticleID=2362
KBase Category Visual DataFlex
Date Created 02/29/2008
Last Edit Date 03/17/2008


Article Text
PROBLEM:
Running a program from the Studio (F5) always compiles, even when not needed in a workspace located on our network (LAN).

SOLUTION:
We discovered that when op-locks are not completely disabled, Windows caches the file timestamp and consequently reports the wrong file timestamp of the .cfg file, causing the Studio/compiler to think compilation is needed every time. The solution is to properly disable op-locks when a workspace is located on the network (as is still recommended for the embedded database).

When the workspace is located on a local hard drive, this problem does not occur, as the problem is related to Windows file sharing and op-locks.



Links Related to this Article
Samba: How important are oplocks?
Tuning Microsoft Networks for the Legacy Embedded Database

Email this Article
Email this Article to a Colleague
Send Feedback on this Article to Data Access Worldwide
Copyright ©2024 Data Access Corporation. All rights reserved.

The information provided in the Data Access Technical Knowledge Base is provided "as is" without warranty of any kind. Data Access Corporation disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Data Access Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Data Access Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.