| RE: [aus-dotnet] OT - IE pagesave failures |
- From: ILT
- Subject: RE: [aus-dotnet] OT - IE pagesave failures
- Date: Thu, 02 Dec 2004 16:53:26 +1100
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Well, as I'm using Win2K and not XP, and Orifice XP (2002, not 2003) it may not be useful to me on this machine. This one does have .NET 1.1 and 2.0 installed, though. Let's see - I have DL one toy and will be interested in how the installer reacts. Ian Thomas GeoSciSoft - Perth, Australia > -----Original Message----- > From: dotnet-owner@xxxxxxxxxxx [mailto:dotnet-owner@xxxxxxxxxxx] On Behalf > Of William Luu > Sent: Thursday, 2 December 2004 1:36 PM > To: 'dotnet@xxxxxxxxxxx' > Subject: RE: [aus-dotnet] OT - IE pagesave failures > > >From memory, we've had this discussion before on the list. > > http://www.stillhq.com/aus-dotnet/archives/msg08387.html > > As I stated before, my workaround is to use the OneNote IE2OneNote plugin > :) > > It really works wonders! > > -- > William Luu > Project Developer > The Grid Corporation > -----Original Message----- > From: ILT [mailto:il.thomas@xxxxxxxxxxxx] > Sent: Thursday, 2 December 2004 4:24 PM > To: dotnet@xxxxxxxxxxx > Subject: [aus-dotnet] OT - IE pagesave failures > > > Curiosity about 1752 and the change to the Gregorian calendar led me to > link > to the page > http://www.ancestry.com/learn/library/article.aspx?article=3358 > and I decided to save it to disk - but IE6 won't play > > I've asked this on MS newsgroups (I hope not here; if so, sorry folks) and > don't get a wholly convincing answer. The work-around I use when I really > want" a page is to print as a PDF file. But that's not always great, > because > some webpages are made for screens at 1400px width and can't print to > paper > (hence, a PDF default A4 pagesize slices off the right margin). > > Any thoughts? > > Ian Thomas > GeoSciSoft - Perth, Australia > -----Original Message----- > From: dotnet-owner@xxxxxxxxxxx [mailto:dotnet-owner@xxxxxxxxxxx] On Behalf > Of Hungerford, Martin (Contractor) > Sent: Thursday, 2 December 2004 10:13 AM > To: 'dotnet@xxxxxxxxxxx' > Subject: RE: [aus-dotnet] #12:00:00 AM# ..is date > > Tim > Your info is correct for England. In Russia, IIRC, the days were > removed > in 1917. > > Martin > -----Original Message----- > From: dotnet-owner@xxxxxxxxxxx [mailto:dotnet-owner@xxxxxxxxxxx]On Behalf > Of > Tim Wilson > Sent: Thursday, 2 December 2004 1:15 PM > To: 'dotnet@xxxxxxxxxxx' > Subject: RE: [aus-dotnet] #12:00:00 AM# ..is date > By the way, do people know why SQL Server uses 1753? > > About 8 years ago I was doing some SCO System admin, when I stumbled > across > some interesting information reading through the "MAN" command (online > manual) pages, looking for information about date-related commands. It's > interesting to note that in September 1752, 11 days were subtracted from > that month in Gregorian calendar (the one used by western society today). > Interestingly SCO Unix displayed a calendar for that month - with exactly > 11 > days missing. > > Curious about the details of the calendar change, do a search for words > "gregorian","1752" and "semptember". eg... > http://www.ancestry.com/learn/library/article.aspx?article=3358 > > .Net uses the same method as SQL for controls DateTimePicker and > MonthCalendar - you cant display it because of a curious mindate. Not much > of a problem for most applications. > > Tim. > -----Original Message----- > From: anthony [mailto:list@xxxxxxxxxxxxxxx] > Sent: Thursday, 18 November 2004 10:57 PM > To: dotnet@xxxxxxxxxxx > Subject: RE: [aus-dotnet] #12:00:00 AM# ..is date > thanks > > > > > From: dotnet-owner@xxxxxxxxxxx [mailto:dotnet-owner@xxxxxxxxxxx] On Behalf > Of Andrew de la Harpe > Sent: Thursday, 18 November 2004 10:02 PM > To: dotnet@xxxxxxxxxxx > Subject: RE: [aus-dotnet] #12:00:00 AM# ..is date > A date always has a value. > Date dt = new Date() = 00:00:00.0000000, January 1, 0001 > Your problem is that this is probably less than the allowed value for your > datatype. > eg SQL Server datetime type has a min value of January 1, 1753 . > > Usually it's best to insert a null for unassigned dates. > ie. if ( dt > DateTime.MinValue) > set param here... > Andrew > -----Original Message----- > From: dotnet-owner@xxxxxxxxxxx [mailto:dotnet-owner@xxxxxxxxxxx]On Behalf > Of > anthony > Sent: Thursday, November 18, 2004 9:55 PM > To: dotnet@xxxxxxxxxxx > Subject: [aus-dotnet] #12:00:00 AM# ..is date > I have property defined as datetime...when i read the property wihout any > assignment the value is #12:00:00 AM# > > if i use isdate..it returns TRUE but this will not submit to SQL...How do > i > detect a valid datetime for SQL? > > > Anthony > _________________ > You are a part of the Australian "dotnet" mailing list. > To unsubscribe send "unsubscribe dotnet" or to re-subscribe send > "subscribe dotnet Your Name" in the body of the email to: > imailsrv@xxxxxxxxxxx > List managed by: http://www.stanski.com _________________ You are a part of the Australian "dotnet" mailing list. To unsubscribe send "unsubscribe dotnet" or to re-subscribe send "subscribe dotnet Your Name" in the body of the email to: imailsrv@xxxxxxxxxxx List managed by: http://www.stanski.com
(Click here for more information on the aus-dotnet mailling list)
- References:
- RE: [aus-dotnet] OT - IE pagesave failures, William Luu
- Prev by Date: RE: [aus-dotnet] OT - IE pagesave failures
- Next by Date: Re: [aus-dotnet] Whidbey Beta2 and the "Go Live"
- Previous by thread: RE: [aus-dotnet] OT - IE pagesave failures
- Next by thread: RE: [aus-dotnet] OT - IE pagesave failures
- Index(es):
