Subject: | |
From: | |
Reply To: | |
Date: | Wed, 24 May 2006 11:55:42 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
On May 24, 2006, at 11:24 AM, Duane L. Mitchell wrote:
> On 5/22/06 9:59 AM Duane L. Mitchell [log in to unmask] said:
>
>> On 5/19/06 10:14 PM John Baxter [log in to unmask] said:
>>
>>> Did the script travel to the client with the problem as a compiled
>>> script containing the reference date?
>>
>> Early on I had them recompile the script on their machine. I was
>> certain
>> that would solve it and was surprised when it didn't.
>
> My curiosity got to me and I visited the site yesterday. Sometimes
> there's
> no substitute for being there and this was the case. Though they
> claimed to
> have re-compiled the scripts they couldn't have because this was
> the first
> thing I did to resolve the issue and it did solve the problem.
>
> Before doing that I ran the script which resulted in a negative
> number. Thus
> pointing to "current date" as the problem in this expression:
>
> ((current date) - pReferenceDate)
>
> I was hoping it would be more interesting than this. I had all the
> various
> solution scripts to try and did not get the chance to run them. I
> suppose
> the question remains how can one create the above expression on a PPC
> machine so that it works on an Intel machine without having to
> recompile.
> Perhaps using one or another of the previously suggested solutions
> for both
> sides of the minus sign would work?
>
> Thanks for the contributions. I learned a bit about dates and date
> math and
> that makes things worthwhile.
With as dynamic as Applescript is there is one other option
on run
set pReferenceDate to run script "date \"january 1, 1904\""
end
-Mark
So would a recalcitrant prostitute be a tough 'ho to road?
|
|
|