In Access, UniqueID would be a field (think column, but not really) and UniqueID would be the name of that field (think column label, like "A"). Based on what you're saying, you need to count how many times a value is in UniqueID field. If that value is constant (e.g. Apple) you can search the field for "Apple" and do a count. However, you want to use the same field for counting values as the field to get the value to count. Access has no such thing as a row number so there is no such thing as the "1" in any field, as Excel (as in A1). You will need a way to locate that value to count.
Easiest way is to use DCount without trying to look up the value: DCount("UniqueID,"Current","UniqueID='Apple'"). Note the nested single quotes for string criteria only.
You might be able to look up the value to count by nesting a DLookup function inside your DCount. However, you will need a field with Unique Values. Obviously that cannot be the field you're trying to count on. If your table is properly designed, you have a primary key - usually an autonumber. Then you probably can refer to the particular row using the PK value that contains your value to count. Say the PK field is named myPK and the value to lookup is in record with pk value of 1. Maybe the DLookup would be like DLookup("UniqueID","Current","myPK = 1"). In English that means "return the value from the UniqueID field in Current table where the PK field value is 1". So the combination might be
DCount("UniqueID","Current",DLookup("UniqueID","Current","myPK = 1))
I have no idea if that will work and I still recommend moving the seed value out of the field being counted instead of convoluted approaches. BTW, it may be good to know where you are intending to use this because using DCount in queries can be a bad idea. If there are a lot of records to count things can get slow. Besides it's considered bad form and that the proper approach is to use sub queries because a DCount function basically does the same thing as a query, but not as efficiently.