Hi folks,
I realize that at this stage of my career I should really understand
the simple stuff. Apparently there's something I don't understand though.
For this scenario, please humor me by assuming that all of the
following is true (some of it is verified by my error logging system,
but the system does not explicitly test each of these assertions):
I have a bunch of VFP tables on a Linux file server.
In the same location is a .dbc file for these tables that is not corrupted.
The connection between the workstation and the server is working.
I do not use private data sessions; all environmental settings are
therefore global.
SET MULTILOCKS is ON
SET EXCLUSIVE is OFF
This is a multi-user application.
The database was explicitly opened: OPEN DATABASE [path\dbc file] SHARED
Many things were done.
Much later, we ensured that all users but this one were logged out,
and created a semaphore file on the server that will prevent any
users from logging back in. We are now in a single-user situation. So we issue:
CLOSE TABLES ALL
CLOSE DATABASES ALL
The database is definitely closed at this point. However, issuing a
correctly-formatted USE command on a table in that database is
supposed to explicitly open the database again.
Next, the code issues:
IF NOT USED [appropriate alias, of which there can be only one for this table]
USE [full correct path\some.dbf] IN 0
ENDIF
The USE line sometimes, but not very often, generates Error 1569
("Database [path\dbc file name]: File access denied").
According to MSDN, I have "attempted to write to a write-protected
database container (.dbc) file."
Again, assuming everything I've told you is true, what could be causing this?
Thanks.
Ken Dibble
www.stic-cil.org
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/AF.CA.24793.797DF865@cdptpa-oedge01
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Virus/security scanners at the server (containing your DBC) was
scanning the DBC?
On Fri, Jan 8, 2016 at 11:37 PM, Ken Dibble <krdibble@stny.rr.com> wrote:
>
> The USE line sometimes, but not very often, generates Error 1569 ("Database
> [path\dbc file name]: File access denied").
>
> According to MSDN, I have "attempted to write to a write-protected database
> container (.dbc) file."
>
> Again, assuming everything I've told you is true, what could be causing
> this?
--
.~. Might, Courage, Vision. SINCERITY!
/ v \ 64-bit Ubuntu 9.10 (Linux kernel 2.6.39.3)
/( _ )\ http://sites.google.com/site/changmw
^ ^ May the Force and farces be with you!
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/CAGv=MJAK8DCTCkvNsK_p8v3n19a8gffD5c1-HUkN7s=PHJDoFg@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Ken,
Just a WAG but check you have TableValidate set to as VFP may well be trying to test the integrity of the table each time you open it and to do this it needs exclusive access.
0: Do not perform table validation.
1: Validate record count when opening a table.
2: Validate record count when appending or inserting records and writing them to disk.
3: Check .dbf header before saving append operation to disk and modifying header.
Default setting is 3 from VFP 8 onwards.
Dave
-----Original Message-----
From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Ken Dibble
Sent: 08 January 2016 15:37
To: profox@leafe.com
Subject: Error 1569
Hi folks,
I realize that at this stage of my career I should really understand the simple stuff. Apparently there's something I don't understand though.
For this scenario, please humor me by assuming that all of the following is true (some of it is verified by my error logging system, but the system does not explicitly test each of these assertions):
I have a bunch of VFP tables on a Linux file server.
In the same location is a .dbc file for these tables that is not corrupted.
The connection between the workstation and the server is working.
I do not use private data sessions; all environmental settings are therefore global.
SET MULTILOCKS is ON
SET EXCLUSIVE is OFF
This is a multi-user application.
The database was explicitly opened: OPEN DATABASE [path\dbc file] SHARED Many things were done.
Much later, we ensured that all users but this one were logged out, and created a semaphore file on the server that will prevent any users from logging back in. We are now in a single-user situation. So we issue:
CLOSE TABLES ALL
CLOSE DATABASES ALL
The database is definitely closed at this point. However, issuing a correctly-formatted USE command on a table in that database is supposed to explicitly open the database again.
Next, the code issues:
IF NOT USED [appropriate alias, of which there can be only one for this table] USE [full correct path\some.dbf] IN 0 ENDIF
The USE line sometimes, but not very often, generates Error 1569 ("Database [path\dbc file name]: File access denied").
According to MSDN, I have "attempted to write to a write-protected database container (.dbc) file."
Again, assuming everything I've told you is true, what could be causing this?
Thanks.
Ken Dibble
www.stic-cil.org
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/18725B8CD2D5D247873A2BAF401D4AB285218C26@EX2010-A-FPL.FPL.LOCAL
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On Fri, 8 Jan 2016, at 03:37 PM, Ken Dibble wrote:
> Again, assuming everything I've told you is true, what could be causing
> this?
The first avenue I would be going down is whether Samba is holding onto
it somehow.
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/1452510255.1971924.488559994.40BC1791@webmail.messagingengine.com
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
On 1/8/2016 10:37 AM, Ken Dibble wrote:
> Hi folks,
>
> I realize that at this stage of my career I should really understand
> the simple stuff. Apparently there's something I don't understand though.
It's not so much "understanding the simple stuff" as it is wading
through the frequent (often useless) underlying OS differences and
quirks from version to version. No one can understand it all.
> For this scenario, please humor me by assuming that all of the
> following is true (some of it is verified by my error logging system,
> but the system does not explicitly test each of these assertions):
...
> CLOSE TABLES ALL
> CLOSE DATABASES ALL
...
> IF NOT USED [appropriate alias, of which there can be only one for
> this table]
> USE [full correct path\some.dbf] IN 0
> ENDIF
>
> The USE line sometimes, but not very often, generates Error 1569
> ("Database [path\dbc file name]: File access denied").
I recommend opening the database (use the OPEN DATABASE command) before
performing the USE statement. And, in fact, if you do you that do not
need to path qualify the DBF (note: I always path qualify my OPEN
DATABASE though <g>).
-Charlie
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/5693DE7D.4090003@verizon.net
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.