Ah, didn't know that. My quick Google of it only mentioned days.

Even if it were just days, it's definitely not that simple when you take into consideration holidays and that some work days are Saturdays in some places/jobs.

I still see those complications with calculating the time.

On 6 September 2018 16:38:11 GMT-04:00, mbsoftwaresolutions@mbsoftwaresolutions.com wrote:

>On 2018-09-05 17:54, Frank Cazabon wrote:

>> I use a calendar table (albeit in SQL server but that shouldn't

>> matter). Then it's just a matter of some simple queries.

>>

>> On 5 September 2018 16:47:27 GMT-04:00,

>> mbsoftwaresolutions@mbsoftwaresolutions.com wrote:

>>> See screenshot for case matter:

>>> https://www.screencast.com/t/VNdRiSd1D

>>>

>>> 1) (rose highlight) I've forgotten how to get Excel to close without

>>> asking me this every time. Currently, I'm just calling the .Quit()

>>> method of my Excel object. I tried passing a .T. parm but that

>>> failed.

>>>

>>> 2) (yellow highlight) Anybody know how to get this slick NETWORKDAYS

>>> formula to work in VFP? Would be neat to have this and I thought

>>> perhaps someone already built it.

>

>

>

>Frank -- it's a slick formula for determining the TIME that's passed

>within the workday hours set (not just days; that'd be simple).

>

[excessive quoting removed by server]

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox

OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/4FDE88F6-66CF-4BEC-A532-1126ABDA541E@gmail.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.