> When I run the following code to create a time stamp
> $dDate := current date
> $hTime := current time
> $lTimeStamp := (($dDate - !01.01.1995!) * 86400) + $hTime
> in A4D and in 4D, I get difference of about 16000 for $lTimeStamp.
> Any idea why?
I am not seeing this. I created a method in 4D, ran the code in Active4D and immediately called the method that runs the same code, and I get the same result. Is Active4D running on Client or Server?
In any case, why not use the Active4D timestamp commands?
I've redid the test today and this time I too get the same result. I'll
investigate into this, when I have more time and report back.
Concerning your suggestion for using the Active4D timestamp commands:
The timestamp is a longint stored in many tables to track modifications
and is updated within a trigger. I used this long before I started to
use A4D. I'd either had to execute the A4D command within an 4D trigger
which probably isn't a good idea or I had to create a 4D method that
mimics the Active4D timestamp command. I decided to do do it the other
way round and create an A4D method with the code from my 4D timestamp
method. That's why I have the same code in 4D and A4D.