Are Lookups what I need (and some other basic questions)?
Posted: Wed Feb 01, 2023 2:46 pm
I am trying to create a new database for my office which revolves around a list of jobs with a date, a client name and a property address. I have 3 tables in total namely:
Instructions table with fields for job number, date, client name, surveyor_id, house name, and road_id.
Surveyors table with fields for primary key (surveyor_id) and surveyor name. (This table has been imported and already holds data)
Roads table with fields for primary key (road_id), road name and postcode. (This table has been imported and already holds about 1,000 records)
Very simply I think I need a main browse and edit form from which I can enter the job number, date, client name, and then I need to be able to select the appropriate surveyor from the related Surveyors table and also the road name from the related Roads table. I am presuming a Lookup is used to get the data from the related table with just the surveyor_id or road_id being saved in the main table but having the browse form show the related surveyor name and road name. (Given that I have 1,000 or so records in the roads table I need to be able to filter these to make selecting the correct road easier). I would appreciate being corrected if I am wrong on the principles behind this and aslo how to make sure the correct field is bound to the main table. I did all this with Access some years ago but am having difficulty getting to grips with nuBuilder.
On a separate note, from the documentation there is reference to naming conventions. Are these critical? Playing around and trying to learn nuBuilder I have deviated from these but it doesn't seem to make any difference as far as I can tell. Examples I am referring to are naming fields with a three digit identifier followed by underscore and using three capital letters for form codes.
The simplest explanation you can bear to give me would be appreciated whilst I try to get off the ground.
Instructions table with fields for job number, date, client name, surveyor_id, house name, and road_id.
Surveyors table with fields for primary key (surveyor_id) and surveyor name. (This table has been imported and already holds data)
Roads table with fields for primary key (road_id), road name and postcode. (This table has been imported and already holds about 1,000 records)
Very simply I think I need a main browse and edit form from which I can enter the job number, date, client name, and then I need to be able to select the appropriate surveyor from the related Surveyors table and also the road name from the related Roads table. I am presuming a Lookup is used to get the data from the related table with just the surveyor_id or road_id being saved in the main table but having the browse form show the related surveyor name and road name. (Given that I have 1,000 or so records in the roads table I need to be able to filter these to make selecting the correct road easier). I would appreciate being corrected if I am wrong on the principles behind this and aslo how to make sure the correct field is bound to the main table. I did all this with Access some years ago but am having difficulty getting to grips with nuBuilder.
On a separate note, from the documentation there is reference to naming conventions. Are these critical? Playing around and trying to learn nuBuilder I have deviated from these but it doesn't seem to make any difference as far as I can tell. Examples I am referring to are naming fields with a three digit identifier followed by underscore and using three capital letters for form codes.
The simplest explanation you can bear to give me would be appreciated whilst I try to get off the ground.