Article View: borland.public.vdbase.data.sql
Article #1262Field Read Only DB7 Browse (BUG?)
From: Wizard
Date: Sat, 21 Mar 1998 00:00
Date: Sat, 21 Mar 1998 00:00
15 lines
1074 bytes
1074 bytes
Ok, in DB5 locking out a field for a browse component was no problem. click the little button in props and it was locked. In DB7 the same procedure is there, but in runtime the feild is not locked. This is a bad thing, perhaps the worst of things. As programer Ego maniacs know, the ability to lock a user out of anything is parramount to the soul. I took a working form from DB5 and ran it in DB7 and it did the same thing. So I have to assume it is a problem within DB7's Visual World. Help would be good. Rewards considered but quickly rejected. :-) TyeSavant@AOL.COM
Technical Details
Message-ID:
<35145880.E8CF6472@aol.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: ff5a1,30d7e50cb065ab80,start X-Google-Attributes: gidff5a1,public From: Wizard <polwizard@aol.com> Subject: Field Read Only DB7 Browse (BUG?) Date: 1998/03/21 Message-ID: <35145880.E8CF6472@aol.com> X-Deja-AN: 336391630 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Organization: Another Netscape Collabra Server User Mime-Version: 1.0 Newsgroups: borland.public.vdbase.data.sql