>I am encountering the following problems on both the client/server and
>trial versions of Oracle Power Objects 1.04.
>Can anyone help me?
>I am running it on a P-100 w/ 16MB RAM and on a 486-DX50 with 20MB
>RAM.
>1. On-line manual says that blaze column attributes (including field
>names) can be changed once saved.
>====> OPO doesn't allow it.
>2. When saving a new table to a newly created blaze database, I get
>the following error messages:
> TBL-04008: Error saving "<table name>" to database
> SES-060060: Database error: PFW-4002: Assertion failed: file
> netsnap\sqlvalue.cpp, line 114
> DBO-05092: Internal error @netsnap\db.cpp:976: bad buffer init
> (0x0,0x0)
>And when I then exit OPO, I get:
> DBO-05092: Internal error @netsnap\db.cpp:976: bad
>Tech support acknowledges the first problem but not the second.
>Any suggestions?
>Your help would be much appreciated.
a) Altering Blaze table definitions is not allowed as of now. This is
actually a documentation error.
b) This error is normally noticed when attempting to save a table in
Blaze containing datatypes RAW/ROWID (with/without indexes). Blaze
does not support datatypes RAW and ROWID. The release notes indicate
that RAW is not supported but apparently miss out ROWID.
sm
>I am encountering the following problems on both the client/server and
>trial versions of Oracle Power Objects 1.04.
>Can anyone help me?
>I am running it on a P-100 w/ 16MB RAM and on a 486-DX50 with 20MB
>RAM.
>1. On-line manual says that blaze column attributes (including field
>names) can be changed once saved.
>====> OPO doesn't allow it.
>2. When saving a new table to a newly created blaze database, I get
>the following error messages:
> TBL-04008: Error saving "<table name>" to database
> SES-060060: Database error: PFW-4002: Assertion failed: file
> netsnap\sqlvalue.cpp, line 114
> DBO-05092: Internal error @netsnap\db.cpp:976: bad buffer init
> (0x0,0x0)
>And when I then exit OPO, I get:
> DBO-05092: Internal error @netsnap\db.cpp:976: bad
>Tech support acknowledges the first problem but not the second.
>Any suggestions?
>Your help would be much appreciated.
After some more playing around, I found that the problem(s) which
generated the above messages are:
a. Datatype ROWID cannot take a size
b. Datatype ROWID cannot be unique or not null
c. Datatype ROWID cannot be used as a primary key.
That's all it was...
*********************************************
Chris Desforges
cw...@cornell.edu
Cornell University
MEng. in Electrical Engineering
*****************************************