1. db_lock_exclusive
I've a question on db_lock_exclusive. If a network user opens a file on a
'server' and locks it, then his computer crashes, how does the locked status
get cleared?. Is this a windows lock that gets cleared by rebooting the
'server'? or are we stuck....?
has anyone found/written a method to rename a table in a db? I've got a few
named inappropriately and would like a tool to rename them instead of
writing a program do copy the records then deleting the original table. on a
long term basis it would be nice to rename tables to "make this years
history file to last years history file" without rebuilding all records into
a new table each time.
george
2. Re: db_lock_exclusive
thanks, Jonas. I haven't got to that point yet. We're trying to develop a
system (with 2 users working over a network) and was wondering on the impact
if one crashes.
george
----- Original Message -----
From: "Jonas Temple" <jktemple at yhti.net>
To: "EUforum" <EUforum at topica.com>
Subject: RE: db_lock_exclusive
>
> George,
>
> This may be way off in left field in response to your question, but you
> might want to consider using the EDS/Net package I put together (in the
> archives). The file can reside on the server and be locked exclusive by
> the local user. When the local user's machine crashes, you would just
> have to "force disconnect" the user from the server to make the file
> available again.
>
> I'd be happy to help with any setup issues or questions.
>
> Jonas
> George Walters wrote:
> > I've a question on db_lock_exclusive. If a network user opens a file on
> > a
> > 'server' and locks it, then his computer crashes, how does the locked
> > status
> > get cleared?. Is this a windows lock that gets cleared by rebooting the
> > 'server'? or are we stuck....?
> >
> > has anyone found/written a method to rename a table in a db? I've got a
> > few
> > named inappropriately and would like a tool to rename them instead of
> > writing a program do copy the records then deleting the original table.
> > on a
> > long term basis it would be nice to rename tables to "make this years
> > history file to last years history file" without rebuilding all records
> > into
> > a new table each time.
> >
> >
> > george
> >
> >
> >
>
>
>
3. Re: db_lock_exclusive
On the topic of 'just changing the name', this would require you to also
change the name in any code that calls the 'last year's' table.
You could always use my 'EDS' interface (Recent user contributions 26 Feb
02) to copy a table to a new named table. The interface makes it a trivial
task to do from the keyboard or from a program. Of course you do have to
master the interface commands first.
A.C.Harper
----- Original Message -----
From: "George Walters" <gwalters at sc.rr.com>
To: "EUforum" <EUforum at topica.com>
Sent: Tuesday, May 21, 2002 4:02 PM
Subject: db_lock_exclusive
>
> I've a question on db_lock_exclusive. If a network user opens a file on a
> 'server' and locks it, then his computer crashes, how does the locked
status
> get cleared?. Is this a windows lock that gets cleared by rebooting the
> 'server'? or are we stuck....?
>
> has anyone found/written a method to rename a table in a db? I've got a
few
> named inappropriately and would like a tool to rename them instead of
> writing a program do copy the records then deleting the original table. on
a
> long term basis it would be nice to rename tables to "make this years
> history file to last years history file" without rebuilding all records
into
> a new table each time.
>
>
> george
>
>
>
>
4. Re: db_lock_exclusive
what i'm invisioning is to
1. delete_table (arHisto)
2. rename_table (arHist, arHisto)
3. create_table(arHist)
This would be quick and not require building all those keys, moving all the
records, etc. None of your programing would have to change subsequent to
this procedure. You always have tables arHist and arHisto.
History files can get quite large.
george
----- Original Message -----
From: <a.c.harper at btinternet.com>
To: "EUforum" <EUforum at topica.com>
Sent: Tuesday, May 21, 2002 3:49 PM
Subject: Re: db_lock_exclusive
>
>
> On the topic of 'just changing the name', this would require you to also
> change the name in any code that calls the 'last year's' table.
>
> You could always use my 'EDS' interface (Recent user contributions 26 Feb
> 02) to copy a table to a new named table. The interface makes it a trivial
> task to do from the keyboard or from a program. Of course you do have to
> master the interface commands first.
>
> A.C.Harper
>
> ----- Original Message -----
> From: "George Walters" <gwalters at sc.rr.com>
> To: "EUforum" <EUforum at topica.com>
> Sent: Tuesday, May 21, 2002 4:02 PM
> Subject: db_lock_exclusive
>
>
> >
> > I've a question on db_lock_exclusive. If a network user opens a file on
a
> > 'server' and locks it, then his computer crashes, how does the locked
> status
> > get cleared?. Is this a windows lock that gets cleared by rebooting the
> > 'server'? or are we stuck....?
> >
> > has anyone found/written a method to rename a table in a db? I've got a
> few
> > named inappropriately and would like a tool to rename them instead of
> > writing a program do copy the records then deleting the original table.
on
> a
> > long term basis it would be nice to rename tables to "make this years
> > history file to last years history file" without rebuilding all records
> into
> > a new table each time.
> >
> >
> > george
> >
> >
> >
>
>
>
