Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread 11013 Error,
Fri, Nov 16 2012 12:42 AMPermanent Link

John Postnikoff

I have created a small utility program with my new DBISAM 4.34 build 4 updates that uses one local and one remote table.

For some reason my DBISAM table that was the local table becomes read only when the program application is transferred to my customer's machine. I am using the exact same paths and table structures when transferring to another computer, as well as sessions. The problem arose when I had to make a slight increase in field size on the new machine, which I could not transfer the local tables from my original machine because data already got populated on the new one by my customer.

I can open the local table with the DBISAM database system utility on my original system and make changes but not on the other machine (my customer's machine).  This is were I get 11013 errors if I try to change the structure, or make changes, without the ability to save. The local table is also read only in the application and also while trying to use dbsys utility on my cusotmer's computer.

I did end up setting my application so it reads all tables as remote tables under the same session name, which seems to work.  I can make changes all around and only in the DBSYS ustility if I open as a remote table. However I still would like access to a single table as a local table on my customer's computer.  What may I be missing?  Also the machine I am trying to transfer to does have applications that are still using DBISAM 4.29  I am wondering if the two versions would effect anything if the all tables reside in the same folder. Any help is appreciated.

John Postnikoff
Tue, Nov 20 2012 12:02 PMPermanent Link

Robert Kaplan

I believe you are running into a problem that occurs when you restructure a
table, the new table gets permissions from the private directory, not the
tables directory.

There is a simple solution that involves copying the table, deleting it and
then copying it back to your tables folder. Try that, if it does not work
look in this forum subject has been discussed many times.

Robert

<John Postnikoff> wrote in message
news:CCE43BBB-C8C4-460E-8D60-6E0DABF04A29@news.elevatesoft.com...
>I have created a small utility program with my new DBISAM 4.34 build 4
>updates that uses one local and one remote table.
>
> For some reason my DBISAM table that was the local table becomes read only
> when the program application is transferred to my customer's machine. I am
> using the exact same paths and table structures when transferring to
> another computer, as well as sessions. The problem arose when I had to
> make a slight increase in field size on the new machine, which I could not
> transfer the local tables from my original machine because data already
> got populated on the new one by my customer.
>
> I can open the local table with the DBISAM database system utility on my
> original system and make changes but not on the other machine (my
> customer's machine).  This is were I get 11013 errors if I try to change
> the structure, or make changes, without the ability to save. The local
> table is also read only in the application and also while trying to use
> dbsys utility on my cusotmer's computer.
>
> I did end up setting my application so it reads all tables as remote
> tables under the same session name, which seems to work.  I can make
> changes all around and only in the DBSYS ustility if I open as a remote
> table. However I still would like access to a single table as a local
> table on my customer's computer.  What may I be missing?  Also the machine
> I am trying to transfer to does have applications that are still using
> DBISAM 4.29  I am wondering if the two versions would effect anything if
> the all tables reside in the same folder. Any help is appreciated.
>
> John Postnikoff
>

Sun, Nov 25 2012 1:48 PMPermanent Link

Walter Matte

Tactical Business Corporation

As Robert said... Permission came from Private Dir....

I set the Session.PrivateDir to be the same folder where the database is, when creating, altering, rebuilding, checking, upgrading,.... tables.

 Session.PrivateDir := DatabasePath;

Walter


>>I believe you are running into a problem that occurs when you restructure a
>>table, the new table gets permissions from the private directory, not the
>>tables directory.
Tue, Dec 11 2012 1:00 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

John,

<< For some reason my DBISAM table that was the local table becomes read
only when the program application is transferred to my customer's machine. I
am using the exact same paths and table structures when transferring to
another computer, as well as sessions. The problem arose when I had to make
a slight increase in field size on the new machine, which I could not
transfer the local tables from my original machine because data already got
populated on the new one by my customer.

I can open the local table with the DBISAM database system utility on my
original system and make changes but not on the other machine (my customer's
machine).  This is were I get 11013 errors if I try to change the structure,
or make changes, without the ability to save. The local table is also read
only in the application and also while trying to use dbsys utility on my
cusotmer's computer. >>

Please see here for more information:

http://www.elevatesoft.com/bulletins?action=view&category=dbisam&bulletin=windows_xp_file_sharing

If you have any other questions, please let me know.

Tim Young
Elevate Software
www.elevatesoft.com
Image