🚀 go-pugleaf

On Tue, 22 Dec 1998 17:31:11 -0500, JonTrimble <jontrimble@juno.com> wrote:

>I have two tables joined (with left outer join checked) with
>an SQL join in a one-to-many (hopefully) relationship
>developed in the SQL Designer.  The resulting SQL statement
>is:
>
>SELECT Cases.Case, Cases.Intake, Cases.ComplName,
>Cases.ComplStreet, Cases.ComplCity, Cases.ComplSt,
>Cases.ComplZip, Cases.ComplPhone, Cases.Relation,
>Cases.Against, Cases.InfoSource, Cases.ComplConsent,
>Cases.ResName, Cases.Gender, Cases.Race, Cases.Age,
>Cases.ResStreet, Cases.ResCity, Cases.ResSt, Cases.ResZip,
>Cases.ResPhone, Cases.ResConsent, Cases.OmbFirstName,
>Cases.OmbLastName, Cases.NumberAffected, Cases.Billing,
>Cases.FacName, Cases.Statement, Cases.Hours, Cases.Expenses,
>Cases.Miles, Cases.Action, Cases.FollowUp, Cases.Closed,
>Complaintcodes.ComplaintCode, Complaintcodes.Case,
>Complaintcodes.Class, Complaintcodes.Resolution,
>Complaintcodes.Referral
>FROM "C:\Program Files\Borland\Visual
>dBASE\Complaints\cases.dbf" Cases
>   LEFT OUTER JOIN "C:\Program Files\Borland\Visual
>dBASE\Complaints\complaintcodes.dbf" Complaintcodes
>   ON  (Complaintcodes.Case = Cases.Case)
>
>The problem I am having is that when I just RUN the SQL file
>I get a Browser which works.  I used the Form Designer to
>design a form with the SQL file as the input.  It appeared
>to work perfectly.  The Add, Delete, Save, Abandon, Top of
>File... icons were on the top Speed Bar as they should be.
>I selected Add and got a new blank row.  I put in some data,
>including data for the child table, and clicked Save.  I got
>an error, which, of course, is not in the Online Help, that
>said Error. Capability does not exist.  This seems to me to
>be a most straight forward app.  I did not write a line of
>code so I do not know what I could have messed up.  I would
>like to get this to work.  Any ideas?

In local SQL (what the BDE uses for dBASE and Paradox tables), all
multi-table queries are read-only. This is true no matter what development
environment you might be using: from Visual dBASE to Delphi to C++Builder.
So any attempt to modify the result set of such a read-only query will
result in an error.

Here is where I get out of my area of expertise. Your dBASE-produced
application is apparently (and, if so, in error) allowing to to make this
attempt. This is dBASE-specific, and nothing to do with the BDE and its
query engine. So perhaps some of the dBASE authorities could explain why
this is possible and how you accommodate read-only queries in Visual dBASE.

//////////////////////////////////////////////////////////////////////////
Steve Koterski                            "Uhn!"
Technical Publications                    -- Ogg the caveman (c. 10,000BC)
INPRISE Corporation
http://www.inprise.com/delphi