If I have a long number that I need to use a lot in calculations &
expressions, is there a way of assigning it a name or something for me
to use i.e. instead of -

[OldMethodologyValue]*1.317122564695

I could have:

[OldMethodologyValue]*Name

Where Name=1.317122564695

If anyone could help I'd really appreciate it.

Regards,

Jay

On Thu, 12 Oct 2006 19:52:43 +0100, Jay <(E-Mail Removed)> wrote:

>If I have a long number that I need to use a lot in calculations &
>expressions, is there a way of assigning it a name or something for me
>to use i.e. instead of -
>
>[OldMethodologyValue]*1.317122564695
>
>I could have:
>
>[OldMethodologyValue]*Name
>
>Where Name=1.317122564695
>
>If anyone could help I'd really appreciate it.
>
>Regards,
>
>Jay

A couple of ways you could do this. One rather crude one would be to
write a dumb little VBA function:

Public Function MyNumber() As Double
MyNumber = 1.317122564695
End Function

and just use MyNumber() in your expression.

If the number will ever vary, it might be better to store it in a
little one-row, one-field table and use DLookUp or a Query to look it
up. With a Query you can just include the table with no join line -
since there's only one row in the table you'll just get the one value.

John W. Vinson[MVP]

Thanks for the suggestions John, I appreciate your help.

Best Regards,

Jay


John Vinson wrote:
> On Thu, 12 Oct 2006 19:52:43 +0100, Jay <(E-Mail Removed)> wrote:
>
>> If I have a long number that I need to use a lot in calculations &
>> expressions, is there a way of assigning it a name or something for me
>> to use i.e. instead of -
>>
>> [OldMethodologyValue]*1.317122564695
>>
>> I could have:
>>
>> [OldMethodologyValue]*Name
>>
>> Where Name=1.317122564695
>>
>> If anyone could help I'd really appreciate it.
>>
>> Regards,
>>
>> Jay
>
> A couple of ways you could do this. One rather crude one would be to
> write a dumb little VBA function:
>
> Public Function MyNumber() As Double
> MyNumber = 1.317122564695
> End Function
>
> and just use MyNumber() in your expression.
>
> If the number will ever vary, it might be better to store it in a
> little one-row, one-field table and use DLookUp or a Query to look it
> up. With a Query you can just include the table with no join line -
> since there's only one row in the table you'll just get the one value.
>
> John W. Vinson[MVP]