From: ruf@herald.usask.ca (Bob Ruf)
Subject: 4D questions (long)
Originator: ruf@herald.usask.ca
Organization: University of Saskatchewan
Date: Thu, 27 Aug 1992 23:42:06 GMT

I'm sorry for the long message, but 4d leads one to ask many questions.


1. EDIT ACCESS

I have a menu selection that has just EDIT ACCESS in its procedure. According 
to the manual, this should bring up the access editor. All that actually 
happens is that the access editor menus flash in the menu bar for a tenth
of a second (est.) and then it goes back to my menu. ?!?!
How do I give the administrator access?

2. The list editor

I want to give the administrator access to the list editor in runtime mode. Do
I have to build a layout and use list to array, etc.?

3. Automatic Relations

I seem to be confused on what is happening with automatic relations. I have two
files (the One and the Many). I made a relation from the Many to the One and
checked the RELATE MANY box. I selected a One record and did an
ADD RECORD([Many]). 4D immediately "loses" my selection in the One file.

In my mind, this shouldn't happen for two reasons:
        a) I didn't check the RELATE ONE box when I made the relation
        b) The manual says that records are loaded into memory but you must use
the RELATE ONE or RELATE MANY commands to make them the current selection for a
file.

I originally got around this problem by not using automatic relations, but I
was cranky because I thought it would be easier if I could. The second work
around was to save the relating field from the One file into a variable and
assign it to the related field in the Many file. When I did this, my One file
selection came back.

What is going on?!?!? (Perhaps an explanation of manual relations would help
too.)

4. Printing labels

I have peoples names in the One file and their addresses in the many file. Are
the following then true:

        a) I can't use the label editor since the fields are in two files
        b) I can't use the export data (and use word to print labels) for the 
same reason
        c) I must either
                i)  populate a "join" file and use a or b
                ii) use an output layout 

5. Strange bug??

I have a no action button on a layout with the following script

SAVE RECORD ([Biographic])
ACCEPT

The layout is "called" by 

ADD RECORD ([Company Contact];*)

--------------------------------------
When I click on the button, the beach ball whirls, and I stay in the layout.
The bio record gets saved, but the company contact record doesn't.

When I trace it, the Debug window "dies" in the layout proc in the after phase.
It gets to the statement 

IF (Before) 

(the first non-comment statement in the proc) and stops executing. 
Note: The whole layou proc is:

If (Before)
        a bunch of lines
end if

The debug window is still displayed, but no buttons work. I can click on the 
layout window behind it and bring it to the front. The dead debug window goes 
beind the layout window and if I bring it to the front again, it is blank (no 
refresh occurs). The layout window is still active and I can click cancel 
with the expected results.


Thanks for any help on any question!!!!!!!
bob
ruf@admin.usask.ca