Prev: AutoOpen() doesn't run!
Next: Macro Error Invalid Argument every other run
From: Peter Jamieson on 21 Jan 2010 13:38
> b. might a good definition, and perhaps explanation of the issues
> involved, very useful.

i.e. might find a good definition... etc.

Peter Jamieson

http://tips.pjmsn.me.uk

On 21/01/2010 18:04, Peter Jamieson wrote:
> BTW, if want to promote the notion of "explicit", may I suggest that you
> put a really good reference to a definition of "explicit" as it applies
> to programming in your messages/sig etc. I suspect many of the people
> who read your messages
> a. don't really know what you mean and
> b. might a good definition, and perhaps explanation of the issues
> involved, very useful.
>
> Best regards,
>
> Peter Jamieson
>
> http://tips.pjmsn.me.uk
>
> On 18/01/2010 21:07, Fumei2 via OfficeKB.com wrote:
>> And thus Jay's warning that it is better to use explicit terms. It is
>> ALWAYS
>> better to be explicit.
>>
>> Debug.Print t + s 456123 appended as a STRING
>> Debug.Print t - s 333 calculated as numbers converted from...and back
>> to...a string
>>
>>
>> Peter Jamieson wrote:
>>> Just to back up your message, "+" is also a string concatenation
>>> operator, e.g. try
>>>
>>> Sub plus()
>>> Dim s As String
>>> Dim t As String
>>> s = "123"
>>> t = "456"
>>> Debug.Print t + s
>>> Debug.Print t - s
>>> End Sub
>>>
>>> Peter Jamieson
>>>
>>> http://tips.pjmsn.me.uk
>>>
>>>> I'm not certain of this, but I think you may find you get that error
>>>> for some combinations of data in the fields and not for others. The
>>> [quoted text clipped - 72 lines]
>>>>> ADO SHAPE Command - Producing Hierarchical Recordsets
>>>>> http://www.eggheadcafe.com/tutorials/aspnet/2e5bf843-ae3d-4ec7-a036-f10d970a8758/ado-shape-command--produ.aspx
>>>>>
>>
First  |  Prev  | 
Pages: 1 2
Prev: AutoOpen() doesn't run!
Next: Macro Error Invalid Argument every other run