Yeah, there is one rule on the table. I'm not sure I can convert this to a
constraint because the rule is rather complicated and has a "not in".
MESSAGE : ERROR: There is already a sale of this item; modify that row's
quantity. If you left Item number blank, DELETE this row with
F9!!!
TABLE : BLADINGDET Row is added or changed if condition SUCCEEDS
WHERE : LotNo IS NULL OR BLLotRecNo NOT IN ( SELECT BLLotRecNo FROM
BladingDet #T1 WHERE #T1.BLLotRecNo = BladingDet.BLLotRecNo )
Karen
-----Original Message-----
From: Dan Goldberg <[email protected]>
To: RBASE-L Mailing List <[email protected]>
Sent: Mon, Dec 3, 2012 1:46 pm
Subject: [RBASE-L] - Re: Slow database, 7.6
Are you running any rule checking on the detail table?
Dan Goldberg
-----Original Message-----
From: Albert Berry
Sent: Monday, December 03, 2012 11:41 AM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Slow database, 7.6
Those are the same settings on my client's server, so that's not the
problem. The documentation suggests that every user needs a CFG file.
Maybe someone else on the list can help - I ran out of ideas.
Albert
On 03/12/2012 12:29 PM, Karen Tellef wrote:
> I checked on the server. It already had "row locks" checked, and
> "column verify". Got excited for a second when I saw your post, but
> it looks okay. Wait time 4, wait interval 5, autorefresh level 0.
>
> Would this be only on the server, or do I need to have every
> workstation checked? I do not make active use of a configuration
> fileand I've never looked at it.
>
> Thanks for the suggestions!
>
> Karen
>
