tenbarge@silver.ucs.indiana.edu (Kris Tenbarge) (02/20/90)
Anyone ever write the udf for dbedit() to include appends when the dbf has a relation set to include another file. Can anyone understand this question? Any Help Appreciated! Kris Tenbarge tenbarge@silver.ucs.indiana.edu
schulz@ipsi.UUCP (Guenther F. Schulz) (02/21/90)
From article <36418@iuvax.cs.indiana.edu>, by tenbarge@silver.ucs.indiana.edu (Kris Tenbarge): > Anyone ever write the udf for dbedit() to include appends when the dbf has a > relation set to include another file. Can anyone understand this question? Yes, I think it's quite clear what you want, but what's your problem? If I see it right you implicitly complain about the non-existing relational capabilities of Clipper, forcing you to explicitly program operations like APPEND or DELETE etc. on secondary tables if a record in the primary table is APPENDed or DELETEd etc..., don't you?? Sorry, but you have to do this in any case, whether you are in the dbedit environment or in a pure Clipper SAY/GET/READ environment. Guenter Schulz
nfs0294@dsac.dla.mil (Glendell R. Midkiff) (02/22/90)
From article <36418@iuvax.cs.indiana.edu>, by tenbarge@silver.ucs.indiana.edu (Kris Tenbarge): > Anyone ever write the udf for dbedit() to include appends when the dbf has a > relation set to include another file. Can anyone understand this question? > I am not sure I fully understand your question, but if you are talking about pulling fields from a related dbf and displaying them in your dbedit window, yes it is not too hard to do. Just write a function that returns a string of all the fields you want. Supply this function name to dbedit() instead of the array of field names. Make sure you have SET RELATION for the related dbf. If you are talking about actually appending records to the dbf, please explain your problem in a little more detail. -- |-----------------------------------------------------------------------| |Glen Midkiff osu-cis!dsacg1!gmidkiff | |From the Internet: gmidkiff@dsac.dla.mil | |Phone: (614)-238-9643 @DLA, Systems Automation Center, Columbus, Oh. |
jgb@prism.gatech.EDU (James G. Baker) (08/31/90)
Clipper '87 added the powerful and sometime dangerous dbedit() function to
attempt to replace dBase's BROWSE. I've stretched it as much as I could
imagine, like the DBU utility, but would *really*, *really* be impressed
and *very* appreciative if there was a way to "lock" a field. That is,
to have one field (leftmost is fine) that would remain as the other
columns scrolled "beneath" it. The locked column needs to stay refreshed
as the database is scrolled vertically, too. Am I dreaming?
Thanks!
--
BAKER,JAMES G - Lab Technician, School of Electrical Engineering
Georgia Institute of Technology, Atlanta Georgia, 30332
uucp: ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!jgb
Internet: jgb@prism.gatech.edu