define fields

[rljapwu]

I have a database that has a text field called 'office'. Each 'office' has a corresponding number field called 'account'. I need to have the number associated with the 'office' automatically put in the 'account' number field when I put the name in the 'office' field. e.g.(If office="naples","091120","") My problem is the calcualtion field only allows so many calcualtions. Is there another way to do this?

[rljapwu]

I have a database that has a text field called 'office'. Each 'office' has a corresponding number field called 'account'. I need to have the number associated with the 'office' automatically put in the 'account' number field when I put the name in the 'office' field. e.g.(If office="naples","091120","") My problem is the calcualtion field only allows so many calcualtions. Is there another way to do this?

[rljapwu]

I have a database that has a text field called 'office'. Each 'office' has a corresponding number field called 'account'. I need to have the number associated with the 'office' automatically put in the 'account' number field when I put the name in the 'office' field. e.g.(If office="naples","091120","") My problem is the calcualtion field only allows so many calcualtions. Is there another way to do this?

[MoonShadow]

Use a relationship. Create a file called Office with two fields, Name and Account Number. Through Define Relationship, join Main:Account Number to Office::AccountNumber. On your Main Account Name, specify Auto-Enter Lookup and select this new relationship and specify the AccountName field.

Create a Value List and base it upon values (all values) from Office file (maybe as popup). Select your Office Account Number field and also display the name. Attach it to your Account Field in Main. You'll be in business.

You could also base your relationship on Name if you are SURE they will remain unique. You could use field validation to do so. Basing it on unique Account Number is the best bet. If you base it on name, then reverse the two fields in the above process - which will only show the Name in the Value List. How many Accounts are we talking about? Because you may wish to filter it a bit or use a portal display instead.

But since you have the Account Number in Main now, you don't really NEED to enter the Office Name data into a field in Main. Just place your Office::Name field directly on your layout in Main.

And welcome to FM forums.

[MoonShadow]

Use a relationship. Create a file called Office with two fields, Name and Account Number. Through Define Relationship, join Main:Account Number to Office::AccountNumber. On your Main Account Name, specify Auto-Enter Lookup and select this new relationship and specify the AccountName field.

Create a Value List and base it upon values (all values) from Office file (maybe as popup). Select your Office Account Number field and also display the name. Attach it to your Account Field in Main. You'll be in business.

You could also base your relationship on Name if you are SURE they will remain unique. You could use field validation to do so. Basing it on unique Account Number is the best bet. If you base it on name, then reverse the two fields in the above process - which will only show the Name in the Value List. How many Accounts are we talking about? Because you may wish to filter it a bit or use a portal display instead.

But since you have the Account Number in Main now, you don't really NEED to enter the Office Name data into a field in Main. Just place your Office::Name field directly on your layout in Main.

And welcome to FM forums.

[MoonShadow]

Use a relationship. Create a file called Office with two fields, Name and Account Number. Through Define Relationship, join Main:Account Number to Office::AccountNumber. On your Main Account Name, specify Auto-Enter Lookup and select this new relationship and specify the AccountName field.

Create a Value List and base it upon values (all values) from Office file (maybe as popup). Select your Office Account Number field and also display the name. Attach it to your Account Field in Main. You'll be in business.

You could also base your relationship on Name if you are SURE they will remain unique. You could use field validation to do so. Basing it on unique Account Number is the best bet. If you base it on name, then reverse the two fields in the above process - which will only show the Name in the Value List. How many Accounts are we talking about? Because you may wish to filter it a bit or use a portal display instead.

But since you have the Account Number in Main now, you don't really NEED to enter the Office Name data into a field in Main. Just place your Office::Name field directly on your layout in Main.

And welcome to FM forums.