wait and sleep effectivley do the same thing, but from the standpoint of the computer WAIT will be eating cpu time counting down and repeatedly checking when it is time to continue, while SLEEP effectivley sets an alarm and lets the computer have cpu time back for other stuff until the program has to continue again, that is what is supposed to happen (and does in other languages or dialects of basic even), but I suspect that sleep and wait do exactly the same thing in DB (ie busy waiting), although I havent tried this to see if this is the case.
Timer() is a system thing that tells you how many milliseconds it was since the system started up, it`s the lowest level of the system that is used by things like the system clock, hardrives and DB to work out the passage of time since power on (the system clock is nowdays a battery backup thing and somewhat seperated from the system clock...in the old days you had to enter the correct time when you started your pc, it actualy stopped the bootup and asked for the time, and then used timer to keep track of the current time by adding the time onto timer()), timer is just best considered as an ever increasing number that tics once per 1000th of a second that you can use to check time in your programs when you are more interested in milliseconds than hours minutes and seconds
cheers.
Mentor.
PC1: P4 hyperthreading 3ghz, 1gig mem, 2x160gig hd`s, ATI radeon 9800 pro gfx, 6 way surround sound, PC2: AMD 1.2ghz, 512mb ram, FX5200 ultra gfx, stereo 16 bit soundblaster, ups.
