Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread Two different database names on same table set
Tue, Nov 19 2013 2:15 PMPermanent Link

John Postnikoff

I am wondering if it is possible and what the implications are of having two different database names setup for the same table set located in the same folder. I would try but do not want to risk corruption,  so I thought I would ask first.  If this is OK to do is there is a possible benefit in another way??

The reason I ask is that I have many C/S client applications to update. I would like to rename the database name in my application. It is impossible to do all client updates at once, unless there is some other method to look at.

Thanks,

John Postnikoff
Tue, Nov 19 2013 4:41 PMPermanent Link

Raul

Globestar Systems

Team Elevate Team Elevate

On 11/19/2013 2:15 PM, John Postnikoff wrote:
> I am wondering if it is possible and what the implications are of having two different database names setup for the same table set located in the same folder. I would try but do not want to risk corruption,  so I thought I would ask first.  If this is OK to do is there is a possible benefit in another way??

I assume you're referring to dbsrvr here. Yes you can definitely do
this. Normal locking and concurrent access rules apply.

I'm not sure what exactly what you're trying to accomplish so can't
offer any other suggestions.

DBISAM database and table handling is very simple (basically files in a
folder) but this also allows for lot of flexibility on how to deal with them

Raul
Wed, Nov 20 2013 10:27 AMPermanent Link

John Postnikoff

Thanks for answers to your questions.  Tests seem to show it works fine. I can now assume then all sessions are controlled by dbsrvr without any implication to what the client side database is named in the database name property.

John


Raul wrote:

On 11/19/2013 2:15 PM, John Postnikoff wrote:
> I am wondering if it is possible and what the implications are of having two different database names setup for the same table set located in the same folder. I would try but do not want to risk corruption,  so I thought I would ask first.  If this is OK to do is there is a possible benefit in another way??

I assume you're referring to dbsrvr here. Yes you can definitely do
this. Normal locking and concurrent access rules apply.

I'm not sure what exactly what you're trying to accomplish so can't
offer any other suggestions.

DBISAM database and table handling is very simple (basically files in a
folder) but this also allows for lot of flexibility on how to deal with them

Raul
Wed, Nov 20 2013 10:30 AMPermanent Link

John Postnikoff

Oops MY questions not yours.  Would be nice to edit a post for spelling and other mistakes.

John Postnikoff wrote:

Thanks for answers to MY questions.  Tests seem to show it works fine. I can now assume then all sessions are controlled by dbsrvr without any implication to what the client side database is named in the database name property.

John


Raul wrote:

On 11/19/2013 2:15 PM, John Postnikoff wrote:
> I am wondering if it is possible and what the implications are of having two different database names setup for the same table set located in the same folder. I would try but do not want to risk corruption,  so I thought I would ask first.  If this is OK to do is there is a possible benefit in another way??

I assume you're referring to dbsrvr here. Yes you can definitely do
this. Normal locking and concurrent access rules apply.

I'm not sure what exactly what you're trying to accomplish so can't
offer any other suggestions.

DBISAM database and table handling is very simple (basically files in a
folder) but this also allows for lot of flexibility on how to deal with them

Raul
Image