BorlandTalk.com

Brandon Lilly · Guest

This is related to MSG: Not including identity column in an insert.

The identity column has been changed to a TIntegerField inside the
DFM, and its ReadOnly property changed to FALSE, and the Provider
flags = [pfInKey] as follows:

object dsDocImportDIM_Key: TIntegerField
FieldName = 'DIM_Key'
ProviderFlags = [pfInKey]
end

Notice that ReadOnly is not set to TRUE (false is default so doesn't
show in DFM). Yet when I run the application, where I assign
dsDocImportDIM_Key.NewValue equal to the newly inserted identity,
DBClient.TCustomClientDataSet.SetFieldData raises an exception because
SOMEHOW dsDocImportDIM_Key.ReadOnly is now TRUE!?!

How can this happen? Nothing in my code except for the part that sets
the identity value after the record inserts is even aware of this
dataset, much less DIM_Key. I have tried forcing ReadOnly = FALSE in
the DFM, but that does no good.

Ideas?

Brandon
--
"In the beginning the universe was created. This has made a lot of
people very angry, and has been widely regarded as a bad move." -
Douglas Noel Adams (1952-2001)

Yuval Malisov · Guest

I had something similar :
When I used "select * from ... order by ..." I noticed that the entire
dataset became read-only.
In the help files I found (after a long search) that if you use select
and don't order by the original
table's key - your dataset becomes read-only. There is another settng:
Also, if you're using TQuery
or something related - you must set RequestLive to True.
I don't know if that's your case, but I hope this helps....

Yuval.

"Brandon Lilly" <brandon.lilly (AT) nospam_medevolve (DOT) com> wrote

Brandon Lilly · Guest

I don't use order by clauses in my queries, preferring to sort on the
client. I am using TADODataSet objects, so I don't think any of the
suggestions will help me here.

Thanks,

Brandon
--
"In the beginning the universe was created. This has made a lot of
people very angry, and has been widely regarded as a bad move." -
Douglas Noel Adams (1952-2001)

lc · Guest

On Thu, 3 Jul 2003 17:43:34 -0500, "Brandon Lilly"
<brandon.lilly (AT) nospam_medevolve (DOT) com> wrote:

Brandon Lilly · Guest

"lc" <lcdata (AT) hotmail (DOT) com> wrote

lc · Guest

On Tue, 8 Jul 2003 15:33:07 -0500, "Brandon Lilly"
<brandon.lilly (AT) nospam_medevolve (DOT) com> wrote:

lc · Guest

On Fri, 11 Jul 2003 11:39:53 -0500, "Brandon Lilly"
<brandon.lilly (AT) nospam_medevolve (DOT) com> wrote:

Brandon Lilly · Guest

"G. Allen Casteran" <allen (AT) nisinc (DOT) com> wrote

Brandon Lilly · Guest

Actually, this is valid functionality - I do this in many other
places.

It is necessary to assign your own value of DIM_Key when working with
multiple records or else you get key violations when you attempt to
post the second inserted record on the client. I assign sequentially
negative numbers for the DIM_Key on the client. In all other
manifestations of this, the value assigned to DIM_Key is ignored in
the insert (since I do not include it in the update). In the
afterupdaterecord event, the actual identity value is reassigned to
the DIM_Key.NewValue so that it can be propogated back to the client.

This is the standard method outlined by Dan Miser
(http://bdn.borland.com/article/0,1410,20847,00.html)

As I mentioned, this is working perfectly fine in many other modules
of our AppServer, so i am confused as to why this particular dataset
is getting these errors. Nothing appears to be different.

Below is the same information for a working set of components for
comparison:

CREATE TABLE dbo.TLocation (
LO_Key int IDENTITY (1, 1) NOT NULL ,
LO_Code varchar (5) NOT NULL ,
LO_Name varchar (40) NOT NULL ,
LO_Address1 varchar (30) NOT NULL ,
LO_Address2 varchar (30) NOT NULL CONSTRAINT
DF__TLocation__LO_Address2 DEFAULT (''),
LO_City varchar (20) NOT NULL ,
LO_State char (2) NOT NULL ,
LO_ZipKey int NOT NULL ,
CONSTRAINT PK__TLocation PRIMARY KEY CLUSTERED (LO_Key) ON PRIMARY
,
CONSTRAINT UQ__TLocation__LO_Code UNIQUE NONCLUSTERED (LO_Code) ON
PRIMARY ,
CONSTRAINT FK__TLocation__LO_State FOREIGN KEY (LO_State) REFERENCES
dbo.TState (ST_Code),
CONSTRAINT FK__TLocation__LO_ZipKey FOREIGN KEY (LO_ZipKey)
REFERENCES dbo.TZip_Code (ZP_Key),
) ON [PRIMARY]

SELECT LO_Key,
LO_Code,
LO_Name,
LO_Address1,
LO_Address2,
LO_City,
LO_State,
LO_ZipKey,
FROM dbo.TLocation
WHERE LO_Key = ISNULL(:LO_Key, LO_Key)
AND LO_Code LIKE ISNULL(:LO_Code, '%')

object dsServiceLocation: TADODataSet
Connection = ConfigConn
CursorType = ctStatic
LockType = ltReadOnly
Parameters = <
item
Name = 'LO_Code'
Attributes = [paNullable]
DataType = ftString
NumericScale = 255
Precision = 255
Size = 5
Value = Null
end
item
Name = 'LO_Key'
Attributes = [paSigned]
DataType = ftInteger
Precision = 10
Size = 4
Value = Null
end>
Left = 36
Top = 288
object dsServiceLocationLO_Key: TIntegerField
FieldName = 'LO_Key'
ProviderFlags = [pfInKey]
end
object dsServiceLocationLO_Code: TStringField
DisplayLabel = 'Code'
FieldName = 'LO_Code'
Size = 5
end
object dsServiceLocationLO_Name: TStringField
DisplayLabel = 'Name'
FieldName = 'LO_Name'
Size = 40
end
object dsServiceLocationLO_Address1: TStringField
DisplayLabel = 'Address1'
FieldName = 'LO_Address1'
Size = 30
end
object dsServiceLocationLO_Address2: TStringField
DefaultExpression = ''''''
DisplayLabel = 'Address2'
FieldName = 'LO_Address2'
Size = 30
end
object dsServiceLocationLO_City: TStringField
DisplayLabel = 'City'
FieldName = 'LO_City'
end
object dsServiceLocationLO_State: TStringField
DisplayLabel = 'State'
FieldName = 'LO_State'
FixedChar = True
Size = 2
end
object dsServiceLocationLO_ZipKey: TIntegerField
FieldName = 'LO_ZipKey'
end
end

Brandon
--
"In the beginning the universe was created. This has made a lot of
people very angry, and has been widely regarded as a bad move." -
Douglas Noel Adams (1952-2001)