This is the table I use:
USE [Calendar] GO
/****** Object: Table [dbo].[Calendar] Script Date: 06/09/2018 06:02:16 PM ******/ SET ANSI_NULLS ON GO
SET QUOTED_IDENTIFIER ON GO
SET ANSI_PADDING ON GO
CREATE TABLE [dbo].[Calendar]( [dt] [date] NOT NULL, [isWeekday] [bit] NULL, [isHoliday] [bit] NULL, [Y] [smallint] NULL, [FY] [smallint] NULL, [Q] [tinyint] NULL, [M] [tinyint] NULL, [D] [tinyint] NULL, [DW] [tinyint] NULL, [monthname] [varchar](9) NULL, [dayname] [varchar](9) NULL, [W] [tinyint] NULL, [HolidayDescription] [varchar](32) NULL, [cal_pk] [int] IDENTITY(1,1) NOT FOR REPLICATION NOT NULL, CONSTRAINT [PK_Calendar] PRIMARY KEY CLUSTERED ( [cal_pk] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY]
GO
SET ANSI_PADDING OFF GO
On 6 September 2018 17:41:04 GMT-04:00, Stephen Russell srussell705@gmail.com wrote:
Do you have a table for Holidays? We use it in our system but it also identifies the country you are in for work. We are USA, CA, UK for now.
I too tried the formula in base format in excel and it returns days when my two cells were 7-30-2018 13:00:00 and 08-01-2018 23:00:00.
I didn't monkey around with cell settings to see if it changed.
On Thu, Sep 6, 2018 at 4:00 PM Frank Cazabon frank.cazabon@gmail.com wrote:
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
- (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.
- (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]