I would like to have a complete copy of a Record Permission field.
For example - I have a field "OWNER" which is Record Permission type.
I want to create another field called "OWNER_COPY" which will always include the value which was selected in the OWNER field.
I thought of few ways to do so but none succeeded:
Crete a new Record Permission field (OWNER_COPY) but it has no option to be calculated (it doesn't have the option: "Set the value of this field using....")
Create calculated Text field (OWNER_COPY)- but if I'm writing [OWNER] in the formula it will provide the ID of the value and not its name.(e.g. if the owner was "Oliver", I will get his id - "123"" in the "OWNER_COPY" field).
Crete regular Text field (OWNER_COPY) and add a rule. but I couldn't find any kind of rule which can fit this case.
Any suggestions?? Thanks in advance :)
Archer can't copy value of RP to anther RP.
I used a custom object for this purpose. The limitation is that the field will be populated only when end user actually interact with a form. The good thing is that the field will be populated instantly.
As an alternative you can use a data feed as Tanveer described above, but in this case there will be a delay between the time when you save the record and population of the 2nd RP field.
Related
I have a table that I saved as a report and created a dashboard that displays the table.
I want to add inputs for each field on the table to be able to filter the table data.
This is the table
I added a text box as the first input
How do I link the text box that has a token called purchCostReferenceToken to the purchCostReference column on the table?
Strictly speaking, the input and the table are not related. The input controls the search and the table is one way to represent the results of the search.
To control the search, use the input token in it. Use dollar signs to denote the token. For example,
index=foo purchCostReference=$purchCostReferenceToken$ | ...
You will need a default value for the token to make this work when no input is provided. Usually, that value is *.
I'm new to MS ACCESS, I would like to know if there is a way to clear an auto number field using a clear button. I've tried to follow some videos on you particularly this one but it seems to be not the proper way on how to deal or create an auto number field.
This is the image is the sample of the form which I'm experimenting with this particular subject.
And this image is the error code which I'm getting right after I clicked the clear button.
[![enter image description here][3]][3]
Below is the code I use for this experiment.
You don't need to clear autonumber field, it handled automatically. So, remove EnployeeID field from INSERT statement and delete rows with Me.txtEmployeeID from clear procedure
The AutoNumber Data Type is assigned automatically and can't be
changed. Also once you enter data into some other field like Employee
Name(New Record event initiated), access will assign a value to the
AutoNumber let's say 1. If you press Esc, access will cancel the edit. Next time you create a new record access will assign the value 2 and so forth. Unless you repair the database then access will reset the AutoNumber counter.
If you want a data type that you change its value, you need to change the Data Type to Number. In this case you need to assign each value by code or by the user input.
The title of this Question may not be accurate because I wasn't sure how to ask the question.
Is there A way to have an ID field in AC 2010 the has a constant part and then a part of the ID that the user will enter in?
EXAMPLE: "EMP9066"
-I would like the "EMP" part of the ID to be constant at all times and the user should not be able to change it and the "9066" is a four digit that the user will be asked to type in.
Please Help.
_ Remember this is not SQL just basic access with some macros.
Thanks
Access has a data type called autonumber which will generate a unique number for each record automatically but it does not allow for the alpha prefix.
if it is indeed constant then the simplest approach is to prefix with it for display, ie in the table the field would be called recId (for example) and you would view the rows via a query with a calculated column
EmpId: "EMP" & format$(RecId,"0000")
What I have here is a table with some text fields. I basically put in the name of some students into a table. I got their info from forms that teachers had sent me. When I put their names into the database, I just put the names in based on which form was at the top. Does access track the actual time that a field was put in in such a way that I could sort my text fields by that so that when I give a list of what I just did to someone else, they won't have to sort through the stack of papers to make sure all of the papers are there?
I should add that I need to track this for an individual field, not just for the record. For instance, let me take this one piece of paper I have. When I get it from an outside agency, I then put it into the database with the student's name and some info. I then need to send it to the teachers for them to sign and send back to me. I am on the second part so the record had already been created, but I want to find the date that I entered the Date_signed field basically.
In this example, you set the default value of the dtmEntered field to Now()
p.s. Same answer as HugoLemos but with a pic :)
You can use a Date/Time field with its default value = Now() to store the time each record is created, as already suggested. That approach works fine when only one user can be adding new records, which sounds like your situation.
If you wish to also store the time an existing record is changed, you can do that from a form's before update event.
This example assumes a text box named txtLast_change which is bound to a Date/Time field in the form's record source. The text box does not have to be visible to the user for this to work.
Private Sub Form_BeforeUpdate(Cancel As Integer)
Me.txtLast_change = Now()
End Sub
Create a field with a date type and set default value to Now()
As you have discovered, there isn't any way after-the-fact to know when data was entered in to your table, as it's not something that you captured in the first place. As you mentioned in one of your comments, you can determine the order in which you entered new records based on the Id, but knowing when additional data was entered would require more tracking fields.
In the future, you may want to think about a table design along these lines:
Column Name Column Description
ID Record Id
STUDENT_ID Student Id Number
STUDENT_FIRST_NAME Student First Name
STUDENT_LAST_NAME Student Last Name
... Other student info ...
DATE_ENTERED Date/Time entered
DATE_SENT Date/Time sent to teacher
DATE_SIGNED Date/Time signed by teacher
UPDATED_DATE Date/Time record last updated
UPDATED_BY User that made the last update
If it's possible, you could always edit your table and add these datestamp columns. You'd have to allow for null values, as the previous entries wouldn't have a date/time value for some of them, but it would let you track future entries.
On a Salesforce.com opportunity I have a number of custom fields that are potential options that the end client will eventually select.
Option 1 (Desc Field) Option 1 (Value)
Option 2 (Desc Field) Option 2 (Value)
Option 3 (Desc Field) Option 3 (Value)
At a future point the user will ultimately choose one of the options as the preferred option. What I want is then the value for the chosen option to be stored in another field without the user having to enter it again. A “nice to have” would also be that all 3 option descriptions, values and selected value are locked once this is done.
Any ideas?
Two things come to mind:
(1) The second field could be a formula field that derives it's answer based on the first field.
(2) A workflow rule using a field update to set the value of the second field, using a formula
(3) A trigger to do the same as #2.
As far as locking, one semi-popular method to lock a page layout is to essentially have two page layouts. The first layout has the fields normally, the second layout has the fields with "read-only". You then create a record type called "Read Only", for example. After the user has entered some specific information in a specific set of fields, a trigger could then check the record type from the normal default one, to the "Read Only" one.
To the user's point of view, the record will be the same, but now he sees it from a different page layout.