Jump to content

Another simple question? re looking up field values

This topic is 5703 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Hi people,

I started my FM career just about 6 weeks ago - progress started well - but since looking at all the wisdom on this site I have become decidedly less confident in knowing the right way to do something - my question on this occasion is to find out whether there is a correct way to ...

to achieve the following:

I have an "activities" table that stores, amongst other things inbound telephone call details.

I have taken the decision that all activities must belong to a "task" and all tasks must belong to a "project" (and all projects to a company).

However our company gets any number of calls where we would not wish to create a project etc for every inbound call so I wish to create a default project for all such calls.

Therefore, when a user creates a new "activity" (where there is no company/project) I want to calculate activities::projectID as a default project ID for an Admin calls project.

Furthermore when a pre-existing client is selected, I want to calculate activities::projectID as the default project for calls for that client (which may change from time to time).

It seems simple but I cannot fathom a simple elegant way of structuring the fields to automatically achieve the above.

All I really want the users to have to do is flag the projects as to what project is the default and what task is the default (say for admin calls)

Any help much appreciated.


Simon :thanks:

Edited by Guest
Link to comment
Share on other sites

This topic is 5703 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.