Re: HELP! W/ 2 table/screen per file
}From: organic@mgr.hjf.org (Miriam Organic) }Subject: HELP! W/ 2 table/screen per file }Date: 5 Jan 1994 20:39:41 GMT }Help me! We have multiple tables (offdrug 1 screen, offstudy 1 screen, }and offdeath 2 screens) in one per file. When 't' is selected to get to }the offdeath table, the second screen of that table comes up and the }cursor rests on the second zza2 fieldtag. It would be REALLY nice if it }went straight to the first screen! Any ideas ?? }Email to organic@mgr.hjf.org I don't think I saw an answer to this posted to comp.databases.informix, but I apologize if there was one in amongst the 400 odd messages I had to deal with today... When you switch the current table in ISQL Perform, it goes to the screen with the most fields on it from the (new) current table. Screen 3 has 6 fields, screen 4 has 5 fields, so I'd expect the cursor to move to screen 3. You say it moves to Screen 4, contrary to my expectations, so I tried to recreate your problem using the form supplied. It is clear that you have not supplied the entire form, and you omitted the whole database schema. All the semi-colons are missing from the attributes section; the field tag d001 is not listed in the screen sections; neither are the fields or_mod_user, os_mod_user, od_mod_user, nor the field tags x, y, z; the field tag zzg is not used. You also give no indication of the product version. It is difficult to answer the question with only half the information... I have some other comments about the form. It is very inflexible to embed full names of databases in the form. It is far better to use DBPATH to locate the database. I will assume that the form layout was to save space in the posting; if not, it looks unbearable to me; however, in the light of the amount of missing information, I assume that a lot of other data has been removed from the form. The trouble is, so much info has been stripped that a proper answer is not possible. Also, why did you strip off the table names from the fields? It at least makes life more difficult for someone like me trying to help from the outside. Why do you need 7 fields (zza2, zzb2, zzc2, zzd2, zzg2, ca, ce) spread over two screens with only 4 lines on the first screen and 3 on the second? Why does the user have to enter the same values in zza, zzb, zzc, zzd and then in zza1, zzb1, zzc1A zzd1, and then in zza2, zzb2, zzc2, zzd2? It would probably be more effective to use the same field tag for all those fields and to join them in the INSTRUCTIONS section. This would also allow you to specify master/detail relationships between the tables. Yours, Jonathan Leffler (johnl@informix.com) #include <disclaimer.h> }DATABASE "/usr/test/HIVTEST/hivtest" }SCREEN { }______Form________Patient______Visit Date______Center__________________________ } [zza ] [zzb ] [zzc ] [zzd] }PERMANENT DISCONTINUATION OF STUDY DRUG(S)_____Check Result [zzg]______________ }Last Date [d000 ] }} SCREEN { }______Form________Patient______Visit Date______Center__________________________ } [zza1 ] [zzb1 ] [zzc1 ] [zzd1] }OFF STUDY___________________________________Check Result [zzg1]________ }} SCREEN { }______Form________Patient______Visit Date______Center__________________________ } [zza2 ] [zzb2 ] [zzc2 ] [zzd2] }DEATH___________________________________Check Result [zzg2]_____________________ }1. Status at time of death [ca] }} SCREEN { }______Form________Patient______Visit Date_____Center____________________________ } [zza2 ] [zzb2 ] [zzc2 ] [zzd2] }DEATH a. Autopsy.........[ce] }} }END }TABLES f_offdrug f_offstudy f_offdeath }ATTRIBUTES }{ Off Drug Block } }zza = or_form }zzb = or_patient }zzc = or_visit_date }zzd = or_center, QUERYCLEAR }d000 = or_lastdate }{ Off Study Block } }zza1 = os_form }zzb1 = os_patient }zzc1 = os_visit_date }zzd1 = os_center, QUERYCLEAR }d001 = os_lastdate }zzg1 = f_offstudy.check_result }{ Off Drug Block } }zza2 = od_form }zzb2 = od_patient }zzc2 = od_visit_date }zzd2 = od_center, QUERYCLEAR }ca = od_status }ce = od_autopsy }zzg2 = f_offdeath.check_result }INSTRUCTIONS }BEFORE EDITUPDATE OF or_mod_user NEXTFIELD = zzb }BEFORE EDITUPDATE OF os_mod_user NEXTFIELD = zzb1 }BEFORE EDITUPDATE OF od_mod_user NEXTFIELD = zzb2 }BEFORE EDITADD OF or_mod_user NEXTFIELD = EXITNOW }BEFORE EDITADD OF os_mod_user NEXTFIELD = EXITNOW }BEFORE EDITADD OF od_mod_user NEXTFIELD = EXITNOW }BEFORE EDITADD EDITUPDATE OF f_offdrug.check_result NEXTFIELD = z }BEFORE EDITADD EDITUPDATE OF f_offstudy.check_result NEXTFIELD = x }BEFORE EDITADD EDITUPDATE OF f_offdeath.check_result NEXTFIELD = y