| equivalent for a comma in separating arguments in functions. Rex's functions accept a string of spaces (or tabs) as an The converter would yield the user's standard format. Know in advance what time format a particular source has, putting it through This last feature would make it unnecessary to No objection to separate functions for the two converion directions, but I'dД¬onsider it quite useful in that case if the output format would also beДЄcceptable as input, so would accept 23.25.59 as input and Well as between minutes and seconds need not be the colon : - e.g. May be in the input, and that the field separator btw. If 'a' or 'p' is in the parameter, assume AM or PM input, Parameter, assume 24-hour format for input, and use 'hh:mm AM' as outputДЇormat.

Time, between AM/PM and 24-hour modes, where the AM/PM may be before orДЄfter the TOD, and may but need not have separating whitespace, and the 'M' If you don't mind a bit more coding, another useful conversion would be for

| there is a format 1 input, and you need output in format 4. | usage would be something like, on a system using format 2 default, | Would you consider adding a new date conversion (maybe in which you can specify both an input and an output format? The Would you consider adding a new date conversion (maybe in which you can specify both an input and an output format? The usage would be something like, on a system using format 2 default, there is a format 1 input, and you need output in format 4. Not a problem, but the HTML page has a misspelling 'Regualar' instead of 'Regular'. Unfortunately, I didn't make a note of it and don't remember which function it is. I found at least one occurrence of a function requiring a final parameter where Rex's version does not require it. I specify mine to be the same place as the LogName directive this makes it easier to find errant coding by examining the log.ДЈ. Error messages appear not to be written to the file specified for error output in the. That was lousy coding on my part, but I've got a ton of 'em and until I get them fixed, I need to use the original functions.Дў. The ISO8601 plugin's functions do not, and simply concatenate two arguments into one, causing a parsing error. Rex's functions accept a string of spaces (or tabs) as an equivalent for a comma in separating arguments in functions. I need to use the original functions until I get all the discrepancies in my coding resolved.ДЎ. They're more like different undocumented behavior for the same not-quite-documented syntax. I agree that my goal would be to completely replace Rex's functions with yours, but there are some undocumented incompatibilities that I would be hard-pressed to describe as bugs. I suspect everyone here understands that, but thanks for saying it. Personally, that limitation does not bother me.ДЇirst, no need to apologize for the work-induced delay. Positive 64-bit 2-s complement signed integer, when the scaling is 100ns, Results are the same, but the domain and range of the functions is reducedДЇor future dates - the limit is 23:59:59 instead of 02:48:05.477 which is the latest epoch that can be represented in a Plug-in functions is for and and even for those the OTOH, the only incompatibility for valid dates between the built-in and the Plug-ins are loaded, the faster TCC operates (at least for some earlier Need both a built-in function and its plug-in overload.

That would be a very significant overhead if within a batch-file loop you | I use this method so that I only have one plugin existing in memory,

| use the command/function/variable/etc., and then

How to use @workday in caseware idea