From accessd at shaw.ca Sun Jun 9 10:56:19 2019 From: accessd at shaw.ca (Jim Lawrence) Date: Sun, 9 Jun 2019 09:56:19 -0600 (MDT) Subject: [dba-Tech] Annoying In-Reply-To: <427146488.110556985.1558306943222.JavaMail.zimbra@shaw.ca> References: <20190517113723.86c3debdd1c3983866efe200e2feb95f.970998f3f2.wbe@email25.godaddy.com> <1845274155.109487644.1558293593975.JavaMail.zimbra@shaw.ca> <427146488.110556985.1558306943222.JavaMail.zimbra@shaw.ca> Message-ID: <33906016.57480941.1560095779966.JavaMail.zimbra@shaw.ca> Hi All: A few days ago, I was testing the Windows 10 partition, on my new laptop and noticed something strange. I had, back in December, installed both the SSH client and SSH server on the Windows section of the device so it could safely access and be accessed from any location. The SSH client is still working but suddenly the SSH server is not functioning. It was very difficult to validate this situation as many previous running Power Shell commands, also stopped working. Working for a solution, over a couple of evenings was going nowhere until I read an article on Microsoft's new direction. It seems that because the new Windows 10 had become such a versatile system people were not buying their servers. To supposedly fix that problem a large series of services, through the regular cycle of updates of the Windows 10 platform, are being removed. Microsoft has been very closed-lipped about this activity but fortunately, unofficial blogs have been logging the depreciation of your desktop machine. :-( The RDP remote connectivity is not and never will be an adequate solution as it is security nightmare (...or any of the numerous remote takeover products that depend on that technology.) Aside: What scum. So much for MS openness. At least we have Linux, where their OS can drive the IoT (Internet of Things) devices, all the way up to the world's largest supercomputers and every computer system in between...one stop shopping. Learn once and run everywhere. Jim From peter.brawley at earthlink.net Sun Jun 9 20:34:15 2019 From: peter.brawley at earthlink.net (Peter Brawley) Date: Sun, 9 Jun 2019 20:34:15 -0500 Subject: [dba-Tech] Annoying In-Reply-To: <33906016.57480941.1560095779966.JavaMail.zimbra@shaw.ca> References: <20190517113723.86c3debdd1c3983866efe200e2feb95f.970998f3f2.wbe@email25.godaddy.com> <1845274155.109487644.1558293593975.JavaMail.zimbra@shaw.ca> <427146488.110556985.1558306943222.JavaMail.zimbra@shaw.ca> <33906016.57480941.1560095779966.JavaMail.zimbra@shaw.ca> Message-ID: <3da8bd84-84d1-81fd-7d40-55dac6a9e166@earthlink.net> On 6/9/2019 10:56, Jim Lawrence wrote: > Hi All: > > A few days ago, I was testing the Windows 10 partition, on my new laptop and noticed something strange. > > I had, back in December, installed both the SSH client and SSH server on the Windows section of the device so it could safely access and be accessed from any location. The SSH client is still working but suddenly the SSH server is not functioning. It was very difficult to validate this situation as many previous running Power Shell commands, also stopped working. > > Working for a solution, over a couple of evenings was going nowhere until I read an article on Microsoft's new direction. It seems that because the new Windows 10 had become such a versatile system people were not buying their servers. To supposedly fix that problem a large series of services, through the regular cycle of updates of the Windows 10 platform, are being removed. Microsoft has been very closed-lipped about this activity but fortunately, unofficial blogs have been logging the depreciation of your desktop machine. :-( Wow. What else are they removing? I disabled Windows Update service at v10.0.14393 (1607), I guess this'll be my last Windows installation. > > The RDP remote connectivity is not and never will be an adequate solution as it is security nightmare (...or any of the numerous remote takeover products that depend on that technology.) > > Aside: What scum. So much for MS openness. At least we have Linux, where their OS can drive the IoT (Internet of Things) devices, all the way up to the world's largest supercomputers and every computer system in between...one stop shopping. Learn once and run everywhere. Yep, "scum" is apt. PB > > Jim > _______________________________________________ > dba-Tech mailing list > dba-Tech at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-tech > Website: http://www.databaseadvisors.com > From jbartow at winhaven.net Sun Jun 9 22:05:23 2019 From: jbartow at winhaven.net (John Bartow) Date: Mon, 10 Jun 2019 03:05:23 +0000 Subject: [dba-Tech] Annoying In-Reply-To: <3da8bd84-84d1-81fd-7d40-55dac6a9e166@earthlink.net> References: <20190517113723.86c3debdd1c3983866efe200e2feb95f.970998f3f2.wbe@email25.godaddy.com> <1845274155.109487644.1558293593975.JavaMail.zimbra@shaw.ca> <427146488.110556985.1558306943222.JavaMail.zimbra@shaw.ca> <33906016.57480941.1560095779966.JavaMail.zimbra@shaw.ca> <3da8bd84-84d1-81fd-7d40-55dac6a9e166@earthlink.net> Message-ID: MS has been the pooch bad lately with their updates. Breaking all sorts of things. IMO the new mgt is trying to move Windows to a Linux core (something akin to what Apple did to Mac OS with X). At this point I'd preaching to the choir if I said they'd be fools otherwise. -----Original Message----- From: dba-Tech On Behalf Of Peter Brawley Sent: Sunday, June 09, 2019 8:34 PM To: dba-tech at databaseadvisors.com Subject: Re: [dba-Tech] Annoying On 6/9/2019 10:56, Jim Lawrence wrote: > Hi All: > > A few days ago, I was testing the Windows 10 partition, on my new laptop and noticed something strange. > > I had, back in December, installed both the SSH client and SSH server on the Windows section of the device so it could safely access and be accessed from any location. The SSH client is still working but suddenly the SSH server is not functioning. It was very difficult to validate this situation as many previous running Power Shell commands, also stopped working. > > Working for a solution, over a couple of evenings was going nowhere > until I read an article on Microsoft's new direction. It seems that > because the new Windows 10 had become such a versatile system people > were not buying their servers. To supposedly fix that problem a large > series of services, through the regular cycle of updates of the > Windows 10 platform, are being removed. Microsoft has been very > closed-lipped about this activity but fortunately, unofficial blogs > have been logging the depreciation of your desktop machine. :-( Wow. What else are they removing? I disabled Windows Update service at v10.0.14393 (1607), I guess this'll be my last Windows installation. > > The RDP remote connectivity is not and never will be an adequate > solution as it is security nightmare (...or any of the numerous remote > takeover products that depend on that technology.) > > Aside: What scum. So much for MS openness. At least we have Linux, where their OS can drive the IoT (Internet of Things) devices, all the way up to the world's largest supercomputers and every computer system in between...one stop shopping. Learn once and run everywhere. Yep, "scum" is apt. PB > > Jim > _______________________________________________ > dba-Tech mailing list > dba-Tech at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-tech > Website: http://www.databaseadvisors.com > _______________________________________________ dba-Tech mailing list dba-Tech at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-tech Website: http://www.databaseadvisors.com From accessd at shaw.ca Sun Jun 9 23:23:00 2019 From: accessd at shaw.ca (Jim Lawrence) Date: Sun, 9 Jun 2019 22:23:00 -0600 (MDT) Subject: [dba-Tech] Annoying In-Reply-To: <3da8bd84-84d1-81fd-7d40-55dac6a9e166@earthlink.net> References: <20190517113723.86c3debdd1c3983866efe200e2feb95f.970998f3f2.wbe@email25.godaddy.com> <1845274155.109487644.1558293593975.JavaMail.zimbra@shaw.ca> <427146488.110556985.1558306943222.JavaMail.zimbra@shaw.ca> <33906016.57480941.1560095779966.JavaMail.zimbra@shaw.ca> <3da8bd84-84d1-81fd-7d40-55dac6a9e166@earthlink.net> Message-ID: <1659362376.61409054.1560140580308.JavaMail.zimbra@shaw.ca> What more can I say, Peter. Jim ----- Original Message ----- From: "peter brawley" To: "Discussion of Hardware and Software issues" Sent: Sunday, June 9, 2019 6:34:15 PM Subject: Re: [dba-Tech] Annoying On 6/9/2019 10:56, Jim Lawrence wrote: > Hi All: > > A few days ago, I was testing the Windows 10 partition, on my new laptop and noticed something strange. > > I had, back in December, installed both the SSH client and SSH server on the Windows section of the device so it could safely access and be accessed from any location. The SSH client is still working but suddenly the SSH server is not functioning. It was very difficult to validate this situation as many previous running Power Shell commands, also stopped working. > > Working for a solution, over a couple of evenings was going nowhere until I read an article on Microsoft's new direction. It seems that because the new Windows 10 had become such a versatile system people were not buying their servers. To supposedly fix that problem a large series of services, through the regular cycle of updates of the Windows 10 platform, are being removed. Microsoft has been very closed-lipped about this activity but fortunately, unofficial blogs have been logging the depreciation of your desktop machine. :-( Wow. What else are they removing? I disabled Windows Update service at v10.0.14393 (1607), I guess this'll be my last Windows installation. > > The RDP remote connectivity is not and never will be an adequate solution as it is security nightmare (...or any of the numerous remote takeover products that depend on that technology.) > > Aside: What scum. So much for MS openness. At least we have Linux, where their OS can drive the IoT (Internet of Things) devices, all the way up to the world's largest supercomputers and every computer system in between...one stop shopping. Learn once and run everywhere. Yep, "scum" is apt. PB > > Jim > _______________________________________________ > dba-Tech mailing list > dba-Tech at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-tech > Website: http://www.databaseadvisors.com > _______________________________________________ dba-Tech mailing list dba-Tech at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-tech Website: http://www.databaseadvisors.com From accessd at shaw.ca Sun Jun 9 23:29:23 2019 From: accessd at shaw.ca (Jim Lawrence) Date: Sun, 9 Jun 2019 22:29:23 -0600 (MDT) Subject: [dba-Tech] Annoying In-Reply-To: References: <20190517113723.86c3debdd1c3983866efe200e2feb95f.970998f3f2.wbe@email25.godaddy.com> <1845274155.109487644.1558293593975.JavaMail.zimbra@shaw.ca> <427146488.110556985.1558306943222.JavaMail.zimbra@shaw.ca> <33906016.57480941.1560095779966.JavaMail.zimbra@shaw.ca> <3da8bd84-84d1-81fd-7d40-55dac6a9e166@earthlink.net> Message-ID: <1223942567.61443993.1560140963926.JavaMail.zimbra@shaw.ca> If Microsoft is moving Windows to a Linux core all I can say is, please hurry, I am drowning here and don't want to be treading-water anymore. I had heard that, about Linux and Windows before but have not read about this improvement yet. Do you have a link or two? Until then I will keep the Champagne on ice. :-) Jim ----- Original Message ----- From: "Discussion of Hardware and Software issues" To: "Discussion of Hardware and Software issues" Cc: "John R Bartow" Sent: Sunday, June 9, 2019 8:05:23 PM Subject: Re: [dba-Tech] Annoying MS has been the pooch bad lately with their updates. Breaking all sorts of things. IMO the new mgt is trying to move Windows to a Linux core (something akin to what Apple did to Mac OS with X). At this point I'd preaching to the choir if I said they'd be fools otherwise. -----Original Message----- From: dba-Tech On Behalf Of Peter Brawley Sent: Sunday, June 09, 2019 8:34 PM To: dba-tech at databaseadvisors.com Subject: Re: [dba-Tech] Annoying On 6/9/2019 10:56, Jim Lawrence wrote: > Hi All: > > A few days ago, I was testing the Windows 10 partition, on my new laptop and noticed something strange. > > I had, back in December, installed both the SSH client and SSH server on the Windows section of the device so it could safely access and be accessed from any location. The SSH client is still working but suddenly the SSH server is not functioning. It was very difficult to validate this situation as many previous running Power Shell commands, also stopped working. > > Working for a solution, over a couple of evenings was going nowhere > until I read an article on Microsoft's new direction. It seems that > because the new Windows 10 had become such a versatile system people > were not buying their servers. To supposedly fix that problem a large > series of services, through the regular cycle of updates of the > Windows 10 platform, are being removed. Microsoft has been very > closed-lipped about this activity but fortunately, unofficial blogs > have been logging the depreciation of your desktop machine. :-( Wow. What else are they removing? I disabled Windows Update service at v10.0.14393 (1607), I guess this'll be my last Windows installation. > > The RDP remote connectivity is not and never will be an adequate > solution as it is security nightmare (...or any of the numerous remote > takeover products that depend on that technology.) > > Aside: What scum. So much for MS openness. At least we have Linux, where their OS can drive the IoT (Internet of Things) devices, all the way up to the world's largest supercomputers and every computer system in between...one stop shopping. Learn once and run everywhere. Yep, "scum" is apt. PB > > Jim > _______________________________________________ > dba-Tech mailing list > dba-Tech at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-tech > Website: http://www.databaseadvisors.com > _______________________________________________ dba-Tech mailing list dba-Tech at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-tech Website: http://www.databaseadvisors.com _______________________________________________ dba-Tech mailing list dba-Tech at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-tech Website: http://www.databaseadvisors.com From peter.brawley at earthlink.net Mon Jun 10 16:06:05 2019 From: peter.brawley at earthlink.net (Peter Brawley) Date: Mon, 10 Jun 2019 16:06:05 -0500 Subject: [dba-Tech] Annoying In-Reply-To: <1223942567.61443993.1560140963926.JavaMail.zimbra@shaw.ca> References: <20190517113723.86c3debdd1c3983866efe200e2feb95f.970998f3f2.wbe@email25.godaddy.com> <1845274155.109487644.1558293593975.JavaMail.zimbra@shaw.ca> <427146488.110556985.1558306943222.JavaMail.zimbra@shaw.ca> <33906016.57480941.1560095779966.JavaMail.zimbra@shaw.ca> <3da8bd84-84d1-81fd-7d40-55dac6a9e166@earthlink.net> <1223942567.61443993.1560140963926.JavaMail.zimbra@shaw.ca> Message-ID: On 6/9/2019 23:29, Jim Lawrence wrote: > If Microsoft is moving Windows to a Linux core all I can say is, please hurry, I am drowning here and don't want to be treading-water anymore. > > I had heard that, about Linux and Windows before but have not read about this improvement yet. Do you have a link or two? Until then I will keep the Champagne on ice. :-) Jim, speaking of transitioning to Linux, is your oreferred Linux file browser KDE Dolphin, or something else? PB ---- > > Jim > > ----- Original Message ----- > From: "Discussion of Hardware and Software issues" > To: "Discussion of Hardware and Software issues" > Cc: "John R Bartow" > Sent: Sunday, June 9, 2019 8:05:23 PM > Subject: Re: [dba-Tech] Annoying > > MS has been the pooch bad lately with their updates. Breaking all sorts of things. > > IMO the new mgt is trying to move Windows to a Linux core (something akin to what Apple did to Mac OS with X). At this point I'd preaching to the choir if I said they'd be fools otherwise. > > -----Original Message----- > From: dba-Tech On Behalf Of Peter Brawley > Sent: Sunday, June 09, 2019 8:34 PM > To: dba-tech at databaseadvisors.com > Subject: Re: [dba-Tech] Annoying > > On 6/9/2019 10:56, Jim Lawrence wrote: >> Hi All: >> >> A few days ago, I was testing the Windows 10 partition, on my new laptop and noticed something strange. >> >> I had, back in December, installed both the SSH client and SSH server on the Windows section of the device so it could safely access and be accessed from any location. The SSH client is still working but suddenly the SSH server is not functioning. It was very difficult to validate this situation as many previous running Power Shell commands, also stopped working. >> >> Working for a solution, over a couple of evenings was going nowhere >> until I read an article on Microsoft's new direction. It seems that >> because the new Windows 10 had become such a versatile system people >> were not buying their servers. To supposedly fix that problem a large >> series of services, through the regular cycle of updates of the >> Windows 10 platform, are being removed. Microsoft has been very >> closed-lipped about this activity but fortunately, unofficial blogs >> have been logging the depreciation of your desktop machine. :-( > Wow. What else are they removing? > > I disabled Windows Update service at v10.0.14393 (1607), I guess this'll be my last Windows installation. > >> The RDP remote connectivity is not and never will be an adequate >> solution as it is security nightmare (...or any of the numerous remote >> takeover products that depend on that technology.) >> >> Aside: What scum. So much for MS openness. At least we have Linux, where their OS can drive the IoT (Internet of Things) devices, all the way up to the world's largest supercomputers and every computer system in between...one stop shopping. Learn once and run everywhere. > Yep, "scum" is apt. > > PB >> Jim >> _______________________________________________ >> dba-Tech mailing list >> dba-Tech at databaseadvisors.com >> http://databaseadvisors.com/mailman/listinfo/dba-tech >> Website: http://www.databaseadvisors.com >> > _______________________________________________ > dba-Tech mailing list > dba-Tech at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-tech > Website: http://www.databaseadvisors.com > > _______________________________________________ > dba-Tech mailing list > dba-Tech at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-tech > Website: http://www.databaseadvisors.com > _______________________________________________ > dba-Tech mailing list > dba-Tech at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-tech > Website: http://www.databaseadvisors.com > From mcp2004 at mail.ru Sat Jun 15 01:43:44 2019 From: mcp2004 at mail.ru (=?UTF-8?B?U2FsYWtoZXRkaW5vdiBTaGFtaWw=?=) Date: Sat, 15 Jun 2019 09:43:44 +0300 Subject: [dba-Tech] =?utf-8?q?Annoying?= In-Reply-To: <1223942567.61443993.1560140963926.JavaMail.zimbra@shaw.ca> References: <20190517113723.86c3debdd1c3983866efe200e2feb95f.970998f3f2.wbe@email25.godaddy.com> <1223942567.61443993.1560140963926.JavaMail.zimbra@shaw.ca> Message-ID: <1560581024.364737963@f545.i.mail.ru> >?Do you have a link or two? WSL 2 ? ( https://devblogs.microsoft.com/commandline/wsl-2-is-now-available-in-windows-insiders/ ) >Monday, June 10, 2019 7:29 AM +03:00 from Jim Lawrence : > >If Microsoft is moving Windows to a Linux core all I can say is, please hurry, I am drowning here and don't want to be treading-water anymore. > >I had heard that, about Linux and Windows before but have not read about this improvement yet. Do you have a link or two? Until then I will keep the Champagne on ice. :-) > >Jim > >----- Original Message ----- >From: "Discussion of Hardware and Software issues" < dba-tech at databaseadvisors.com > >To: "Discussion of Hardware and Software issues" < dba-tech at databaseadvisors.com > >Cc: "John R Bartow" < jbartow at winhaven.net > >Sent: Sunday, June 9, 2019 8:05:23 PM >Subject: Re: [dba-Tech] Annoying > >MS has been the pooch bad lately with their updates. Breaking all sorts of things. > >IMO the new mgt is trying to move Windows to a Linux core (something akin to what Apple did to Mac OS with X). At this point I'd preaching to the choir if I said they'd be fools otherwise. > >-----Original Message----- >From: dba-Tech < dba-tech-bounces at databaseadvisors.com > On Behalf Of Peter Brawley >Sent: Sunday, June 09, 2019 8:34 PM >To: dba-tech at databaseadvisors.com >Subject: Re: [dba-Tech] Annoying > >On 6/9/2019 10:56, Jim Lawrence wrote: >> Hi All: >> >> A few days ago, I was testing the Windows 10 partition, on my new laptop and noticed something strange. >> >> I had, back in December, installed both the SSH client and SSH server on the Windows section of the device so it could safely access and be accessed from any location. The SSH client is still working but suddenly the SSH server is not functioning. It was very difficult to validate this situation as many previous running Power Shell commands, also stopped working. >> >> Working for a solution, over a couple of evenings was going nowhere >> until I read an article on Microsoft's new direction. It seems that >> because the new Windows 10 had become such a versatile system people >> were not buying their servers. To supposedly fix that problem a large >> series of services, through the regular cycle of updates of the >> Windows 10 platform, are being removed. Microsoft has been very >> closed-lipped about this activity but fortunately, unofficial blogs >> have been logging the depreciation of your desktop machine. :-( > >Wow. What else are they removing? > >I disabled Windows Update service at v10.0.14393 (1607), I guess this'll be my last Windows installation. > >> >> The RDP remote connectivity is not and never will be an adequate >> solution as it is security nightmare (...or any of the numerous remote >> takeover products that depend on that technology.) >> >> Aside: What scum. So much for MS openness. At least we have Linux, where their OS can drive the IoT (Internet of Things) devices, all the way up to the world's largest supercomputers and every computer system in between...one stop shopping. Learn once and run everywhere. > >Yep, "scum" is apt. > >PB >> >> Jim >> _______________________________________________ From accessd at shaw.ca Mon Jun 17 21:05:59 2019 From: accessd at shaw.ca (Jim Lawrence) Date: Mon, 17 Jun 2019 20:05:59 -0600 (MDT) Subject: [dba-Tech] Annoying In-Reply-To: <1560581024.364737963@f545.i.mail.ru> References: <20190517113723.86c3debdd1c3983866efe200e2feb95f.970998f3f2.wbe@email25.godaddy.com> <1223942567.61443993.1560140963926.JavaMail.zimbra@shaw.ca> <1560581024.364737963@f545.i.mail.ru> Message-ID: <1219733764.123918129.1560823559099.JavaMail.zimbra@shaw.ca> Linux having its own virtual machine within Windows is definitely better than the WSL. Aside: I have always wondered why it has been called WSL as it really should be called LSW, Linux Subsystem for Windows...but what do I know. If this new VM has no limitations and an additional OS IP address can be created then there can be a SSH server, for a Windows10 box and a huge group of other features become available. Of course it asks the next question; why run Windows as the VM host. It is much better suited as a client to a Linux host. :-) Jim ----- Original Message ----- From: "Discussion of Hardware and Software issues" To: "Discussion of Hardware and Software issues" Cc: "Salakhetdinov Shamil" Sent: Friday, June 14, 2019 11:43:44 PM Subject: Re: [dba-Tech] Annoying >?Do you have a link or two? WSL 2 ? ( https://devblogs.microsoft.com/commandline/wsl-2-is-now-available-in-windows-insiders/ ) >Monday, June 10, 2019 7:29 AM +03:00 from Jim Lawrence : > >If Microsoft is moving Windows to a Linux core all I can say is, please hurry, I am drowning here and don't want to be treading-water anymore. > >I had heard that, about Linux and Windows before but have not read about this improvement yet. Do you have a link or two? Until then I will keep the Champagne on ice. :-) > >Jim > >----- Original Message ----- >From: "Discussion of Hardware and Software issues" < dba-tech at databaseadvisors.com > >To: "Discussion of Hardware and Software issues" < dba-tech at databaseadvisors.com > >Cc: "John R Bartow" < jbartow at winhaven.net > >Sent: Sunday, June 9, 2019 8:05:23 PM >Subject: Re: [dba-Tech] Annoying > >MS has been the pooch bad lately with their updates. Breaking all sorts of things. > >IMO the new mgt is trying to move Windows to a Linux core (something akin to what Apple did to Mac OS with X). At this point I'd preaching to the choir if I said they'd be fools otherwise. > >-----Original Message----- >From: dba-Tech < dba-tech-bounces at databaseadvisors.com > On Behalf Of Peter Brawley >Sent: Sunday, June 09, 2019 8:34 PM >To: dba-tech at databaseadvisors.com >Subject: Re: [dba-Tech] Annoying > >On 6/9/2019 10:56, Jim Lawrence wrote: >> Hi All: >> >> A few days ago, I was testing the Windows 10 partition, on my new laptop and noticed something strange. >> >> I had, back in December, installed both the SSH client and SSH server on the Windows section of the device so it could safely access and be accessed from any location. The SSH client is still working but suddenly the SSH server is not functioning. It was very difficult to validate this situation as many previous running Power Shell commands, also stopped working. >> >> Working for a solution, over a couple of evenings was going nowhere >> until I read an article on Microsoft's new direction. It seems that >> because the new Windows 10 had become such a versatile system people >> were not buying their servers. To supposedly fix that problem a large >> series of services, through the regular cycle of updates of the >> Windows 10 platform, are being removed. Microsoft has been very >> closed-lipped about this activity but fortunately, unofficial blogs >> have been logging the depreciation of your desktop machine. :-( > >Wow. What else are they removing? > >I disabled Windows Update service at v10.0.14393 (1607), I guess this'll be my last Windows installation. > >> >> The RDP remote connectivity is not and never will be an adequate >> solution as it is security nightmare (...or any of the numerous remote >> takeover products that depend on that technology.) >> >> Aside: What scum. So much for MS openness. At least we have Linux, where their OS can drive the IoT (Internet of Things) devices, all the way up to the world's largest supercomputers and every computer system in between...one stop shopping. Learn once and run everywhere. > >Yep, "scum" is apt. > >PB >> >> Jim >> _______________________________________________ _______________________________________________ dba-Tech mailing list dba-Tech at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-tech Website: http://www.databaseadvisors.com From accessd at shaw.ca Mon Jun 17 21:47:58 2019 From: accessd at shaw.ca (Jim Lawrence) Date: Mon, 17 Jun 2019 20:47:58 -0600 (MDT) Subject: [dba-Tech] 10 things that Linux can do.. In-Reply-To: <1219733764.123918129.1560823559099.JavaMail.zimbra@shaw.ca> References: <20190517113723.86c3debdd1c3983866efe200e2feb95f.970998f3f2.wbe@email25.godaddy.com> <1223942567.61443993.1560140963926.JavaMail.zimbra@shaw.ca> <1560581024.364737963@f545.i.mail.ru> <1219733764.123918129.1560823559099.JavaMail.zimbra@shaw.ca> Message-ID: <1479550608.124161991.1560826078943.JavaMail.zimbra@shaw.ca> ...that Windows can not or does not do. Here are ten important features that put Linux into a new level: https://youtu.be/JOOkfGv58u0 Aside: 16,000 developers are working on core Linux at any one time. That is the real reason why Linux is so far ahead of Windows. ;-) Jim From ssharkins at gmail.com Fri Jun 21 08:08:07 2019 From: ssharkins at gmail.com (Susan Harkins) Date: Fri, 21 Jun 2019 09:08:07 -0400 Subject: [dba-Tech] VBS question Message-ID: <018401d52832$5f56fd70$1e04f850$@gmail.com> Do any of you use .vbs scripts to interact with an Excel workbook? I've written one to run from Windows Task Scheduler. It simply triggers a print macro (prints a PivotTable) daily. The macro in Excel works. The task is running, but the PivotTable never prints. This is rather new to me, so I'm sure it's a simple fix, probably in one of the referencing statements. Can someone take a look? I've tried several variations of referencing the macro. '.vbs file to print Excel PivoTable1.xlsm at 8am daily. 'Path to workbook. strPath = "C:\Documents\PivotTable1.xlsm" 'Macro name. strMacro = "PrintUpdatedPivotTable" 'Create an Excel instance. Set objApp = CreateObject("Excel.Application") Set objwb = objExcel.Workbooks.Open(strPath) objApp.Visible = True objApp.Run strMacro objwb.Close objApp.Quit 'Scheduled task completed. MsgBox strPath & " " & strMacro & " PivotTable printed successfully", vbInformation Susan H. From df.waters at outlook.com Fri Jun 21 08:16:50 2019 From: df.waters at outlook.com (Daniel Waters) Date: Fri, 21 Jun 2019 13:16:50 +0000 Subject: [dba-Tech] VBS question In-Reply-To: <018401d52832$5f56fd70$1e04f850$@gmail.com> References: <018401d52832$5f56fd70$1e04f850$@gmail.com> Message-ID: Hi Susan, I don't work with VBS, but the logic in the script looks right. 2 questions? Is the VBS script actually able to call the macro? Could you run the printer from the VBS script manually? Also - it might just be syntax where you need to use the actual name of the macro in double quotes instead of a variable name. Good Luck! Dan -----Original Message----- From: dba-Tech [mailto:dba-tech-bounces at databaseadvisors.com] On Behalf Of Susan Harkins Sent: June 21, 2019 8:08 To: Discussion of Hardware and Software issues Subject: [dba-Tech] VBS question Do any of you use .vbs scripts to interact with an Excel workbook? I've written one to run from Windows Task Scheduler. It simply triggers a print macro (prints a PivotTable) daily. The macro in Excel works. The task is running, but the PivotTable never prints. This is rather new to me, so I'm sure it's a simple fix, probably in one of the referencing statements. Can someone take a look? I've tried several variations of referencing the macro. '.vbs file to print Excel PivoTable1.xlsm at 8am daily. 'Path to workbook. strPath = "C:\Documents\PivotTable1.xlsm" 'Macro name. strMacro = "PrintUpdatedPivotTable" 'Create an Excel instance. Set objApp = CreateObject("Excel.Application") Set objwb = objExcel.Workbooks.Open(strPath) objApp.Visible = True objApp.Run strMacro objwb.Close objApp.Quit 'Scheduled task completed. MsgBox strPath & " " & strMacro & " PivotTable printed successfully", vbInformation Susan H. _______________________________________________ dba-Tech mailing list dba-Tech at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-tech Website: http://www.databaseadvisors.com From gustav at cactus.dk Fri Jun 21 08:23:00 2019 From: gustav at cactus.dk (Gustav Brock) Date: Fri, 21 Jun 2019 13:23:00 +0000 Subject: [dba-Tech] VBS question Message-ID: Hi Susan Excel is very picky with its objects. So, try: '.vbs file to print Excel PivoTable1.xlsm at 8am daily. 'Path to workbook. strPath = "C:\Documents\PivotTable1.xlsm" 'Macro name. strMacro = "PrintUpdatedPivotTable" 'Create an Excel instance. Set objApp = CreateObject("Excel.Application") Set objwb = objExcel.Workbooks.Open(strPath) objApp.Visible = True ' Should not be needed. objApp.Run strMacro objwb.Close Set objwb = Nothing objApp.Quit Set objApp = Nothing 'Scheduled task completed. MsgBox strPath & " " & strMacro & " PivotTable printed successfully", vbInformation Also, check that no Excel instance is left open after running the script. -----Oprindelig meddelelse----- Fra: dba-Tech P? vegne af Susan Harkins Sendt: 21. juni 2019 15:08 Til: Discussion of Hardware and Software issues Emne: [dba-Tech] VBS question Do any of you use .vbs scripts to interact with an Excel workbook? I've written one to run from Windows Task Scheduler. It simply triggers a print macro (prints a PivotTable) daily. The macro in Excel works. The task is running, but the PivotTable never prints. This is rather new to me, so I'm sure it's a simple fix, probably in one of the referencing statements. Can someone take a look? I've tried several variations of referencing the macro. '.vbs file to print Excel PivoTable1.xlsm at 8am daily. 'Path to workbook. strPath = "C:\Documents\PivotTable1.xlsm" 'Macro name. strMacro = "PrintUpdatedPivotTable" 'Create an Excel instance. Set objApp = CreateObject("Excel.Application") Set objwb = objExcel.Workbooks.Open(strPath) objApp.Visible = True objApp.Run strMacro objwb.Close objApp.Quit 'Scheduled task completed. MsgBox strPath & " " & strMacro & " PivotTable printed successfully", vbInformation Susan H. From ssharkins at gmail.com Fri Jun 21 09:00:59 2019 From: ssharkins at gmail.com (Susan Harkins) Date: Fri, 21 Jun 2019 10:00:59 -0400 Subject: [dba-Tech] VBS question In-Reply-To: References: Message-ID: <01e001d52839$c1fcba30$45f62e90$@gmail.com> Thanks Gustav -- still not working. I dropped in a cell(1,"A").Value = Time() statement just test and it doesn't work either -- the script is running -- I can see the Echo on the screen. Not sure how to continue troubleshooting. Is it possible that it's something with my Task Scheduler settings? The Action is Start a program. The Program/script is C:\Windows\Systems32\cscript.exe. The only argment is "C:\Users\Susan Harkins\Documents\PrintPivotTable.vbs" I have the visible property set to True and I thought I would see Excel quickly open, but that doesn't happen. Should it? Susan H. tech at databaseadvisors.com> Subject: Re: [dba-Tech] VBS question Hi Susan Excel is very picky with its objects. So, try: '.vbs file to print Excel PivoTable1.xlsm at 8am daily. 'Path to workbook. strPath = "C:\Documents\PivotTable1.xlsm" 'Macro name. strMacro = "PrintUpdatedPivotTable" 'Create an Excel instance. Set objApp = CreateObject("Excel.Application") Set objwb = objExcel.Workbooks.Open(strPath) objApp.Visible = True ' Should not be needed. objApp.Run strMacro objwb.Close Set objwb = Nothing objApp.Quit Set objApp = Nothing 'Scheduled task completed. MsgBox strPath & " " & strMacro & " PivotTable printed successfully", vbInformation Also, check that no Excel instance is left open after running the script. From ssharkins at gmail.com Fri Jun 21 09:02:11 2019 From: ssharkins at gmail.com (Susan Harkins) Date: Fri, 21 Jun 2019 10:02:11 -0400 Subject: [dba-Tech] VBS question In-Reply-To: References: Message-ID: <01eb01d52839$ec962f10$c5c28d30$@gmail.com> Also -- yesterday, I turned off macro control while testing -- I thought perhaps that might be a problem -- made no difference. Susan H. Hi Susan Excel is very picky with its objects. So, try: '.vbs file to print Excel PivoTable1.xlsm at 8am daily. 'Path to workbook. strPath = "C:\Documents\PivotTable1.xlsm" 'Macro name. strMacro = "PrintUpdatedPivotTable" 'Create an Excel instance. Set objApp = CreateObject("Excel.Application") Set objwb = objExcel.Workbooks.Open(strPath) objApp.Visible = True ' Should not be needed. objApp.Run strMacro objwb.Close Set objwb = Nothing objApp.Quit Set objApp = Nothing 'Scheduled task completed. MsgBox strPath & " " & strMacro & " PivotTable printed successfully", vbInformation Also, check that no Excel instance is left open after running the script. -----Oprindelig meddelelse----- Fra: dba-Tech P? vegne af Susan Harkins Sendt: 21. juni 2019 15:08 Til: Discussion of Hardware and Software issues Emne: [dba-Tech] VBS question Do any of you use .vbs scripts to interact with an Excel workbook? I've written one to run from Windows Task Scheduler. It simply triggers a print macro (prints a PivotTable) daily. The macro in Excel works. The task is running, but the PivotTable never prints. This is rather new to me, so I'm sure it's a simple fix, probably in one of the referencing statements. Can someone take a look? I've tried several variations of referencing the macro. '.vbs file to print Excel PivoTable1.xlsm at 8am daily. 'Path to workbook. strPath = "C:\Documents\PivotTable1.xlsm" 'Macro name. strMacro = "PrintUpdatedPivotTable" 'Create an Excel instance. Set objApp = CreateObject("Excel.Application") Set objwb = objExcel.Workbooks.Open(strPath) objApp.Visible = True objApp.Run strMacro objwb.Close objApp.Quit 'Scheduled task completed. MsgBox strPath & " " & strMacro & " PivotTable printed successfully", vbInformation Susan H. _______________________________________________ dba-Tech mailing list dba-Tech at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-tech Website: http://www.databaseadvisors.com From gustav at cactus.dk Fri Jun 21 09:16:27 2019 From: gustav at cactus.dk (Gustav Brock) Date: Fri, 21 Jun 2019 14:16:27 +0000 Subject: [dba-Tech] VBS question Message-ID: Hi Susan It could be that it doesn't run using your account. Try moving the script and workbook to the Shared/Public Documents folder. /gustav -----Oprindelig meddelelse----- Fra: dba-Tech P? vegne af Susan Harkins Sendt: 21. juni 2019 16:01 Til: 'Discussion of Hardware and Software issues' Emne: Re: [dba-Tech] VBS question Thanks Gustav -- still not working. I dropped in a cell(1,"A").Value = Time() statement just test and it doesn't work either -- the script is running -- I can see the Echo on the screen. Not sure how to continue troubleshooting. Is it possible that it's something with my Task Scheduler settings? The Action is Start a program. The Program/script is C:\Windows\Systems32\cscript.exe. The only argment is "C:\Users\Susan Harkins\Documents\PrintPivotTable.vbs" I have the visible property set to True and I thought I would see Excel quickly open, but that doesn't happen. Should it? Susan H. tech at databaseadvisors.com> Subject: Re: [dba-Tech] VBS question Hi Susan Excel is very picky with its objects. So, try: '.vbs file to print Excel PivoTable1.xlsm at 8am daily. 'Path to workbook. strPath = "C:\Documents\PivotTable1.xlsm" 'Macro name. strMacro = "PrintUpdatedPivotTable" 'Create an Excel instance. Set objApp = CreateObject("Excel.Application") Set objwb = objExcel.Workbooks.Open(strPath) objApp.Visible = True ' Should not be needed. objApp.Run strMacro objwb.Close Set objwb = Nothing objApp.Quit Set objApp = Nothing 'Scheduled task completed. MsgBox strPath & " " & strMacro & " PivotTable printed successfully", vbInformation Also, check that no Excel instance is left open after running the script. From ssharkins at gmail.com Fri Jun 21 16:40:15 2019 From: ssharkins at gmail.com (Susan Harkins) Date: Fri, 21 Jun 2019 17:40:15 -0400 Subject: [dba-Tech] VBS question In-Reply-To: References: Message-ID: <00bb01d52879$ea6b92d0$bf42b870$@gmail.com> It's working now. I had a misnamed variable (ugh). I hate that kind of problem -- hard to find yourself. I left it and planted flowers in the garden I maintain as volunteer. Came back and spotted it right away. I have two more questions though: 1.) I don't want to close all instances of Excel, just the one that's running the macro. I don't want to inadvertently shut someone down who might be using Excel. 2.) I want to inhibit the Excel Save when exiting prompt. Should I do this in the Excel procedure or in the VBS script? Thanks everyone for your help today. Susan H. Hi Susan It could be that it doesn't run using your account. Try moving the script and workbook to the Shared/Public Documents folder. /gustav -----Oprindelig meddelelse----- Fra: dba-Tech P? vegne af Susan Harkins Sendt: 21. juni 2019 16:01 Til: 'Discussion of Hardware and Software issues' Emne: Re: [dba-Tech] VBS question Thanks Gustav -- still not working. I dropped in a cell(1,"A").Value = Time() statement just test and it doesn't work either -- the script is running -- I can see the Echo on the screen. Not sure how to continue troubleshooting. Is it possible that it's something with my Task Scheduler settings? The Action is Start a program. The Program/script is C:\Windows\Systems32\cscript.exe. The only argment is "C:\Users\Susan Harkins\Documents\PrintPivotTable.vbs" I have the visible property set to True and I thought I would see Excel quickly open, but that doesn't happen. Should it? Susan H. tech at databaseadvisors.com> Subject: Re: [dba-Tech] VBS question Hi Susan Excel is very picky with its objects. So, try: '.vbs file to print Excel PivoTable1.xlsm at 8am daily. 'Path to workbook. strPath = "C:\Documents\PivotTable1.xlsm" 'Macro name. strMacro = "PrintUpdatedPivotTable" 'Create an Excel instance. Set objApp = CreateObject("Excel.Application") Set objwb = objExcel.Workbooks.Open(strPath) objApp.Visible = True ' Should not be needed. objApp.Run strMacro objwb.Close Set objwb = Nothing objApp.Quit Set objApp = Nothing 'Scheduled task completed. MsgBox strPath & " " & strMacro & " PivotTable printed successfully", vbInformation Also, check that no Excel instance is left open after running the script. _______________________________________________ dba-Tech mailing list dba-Tech at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-tech Website: http://www.databaseadvisors.com From ssharkins at gmail.com Fri Jun 21 16:40:15 2019 From: ssharkins at gmail.com (Susan Harkins) Date: Fri, 21 Jun 2019 17:40:15 -0400 Subject: [dba-Tech] VBS question In-Reply-To: References: Message-ID: <00bc01d52879$eb9e9490$c2dbbdb0$@gmail.com> I don't have that structure. I shared the documents folder -- still nothing. -----Original Message----- From: dba-Tech On Behalf Of Gustav Brock Sent: Friday, June 21, 2019 10:16 AM To: Discussion of Hardware and Software issues Subject: Re: [dba-Tech] VBS question Hi Susan It could be that it doesn't run using your account. Try moving the script and workbook to the Shared/Public Documents folder. /gustav -----Oprindelig meddelelse----- Fra: dba-Tech P? vegne af Susan Harkins Sendt: 21. juni 2019 16:01 Til: 'Discussion of Hardware and Software issues' Emne: Re: [dba-Tech] VBS question Thanks Gustav -- still not working. I dropped in a cell(1,"A").Value = Time() statement just test and it doesn't work either -- the script is running -- I can see the Echo on the screen. Not sure how to continue troubleshooting. Is it possible that it's something with my Task Scheduler settings? The Action is Start a program. The Program/script is C:\Windows\Systems32\cscript.exe. The only argment is "C:\Users\Susan Harkins\Documents\PrintPivotTable.vbs" I have the visible property set to True and I thought I would see Excel quickly open, but that doesn't happen. Should it? Susan H. tech at databaseadvisors.com> Subject: Re: [dba-Tech] VBS question Hi Susan Excel is very picky with its objects. So, try: '.vbs file to print Excel PivoTable1.xlsm at 8am daily. 'Path to workbook. strPath = "C:\Documents\PivotTable1.xlsm" 'Macro name. strMacro = "PrintUpdatedPivotTable" 'Create an Excel instance. Set objApp = CreateObject("Excel.Application") Set objwb = objExcel.Workbooks.Open(strPath) objApp.Visible = True ' Should not be needed. objApp.Run strMacro objwb.Close Set objwb = Nothing objApp.Quit Set objApp = Nothing 'Scheduled task completed. MsgBox strPath & " " & strMacro & " PivotTable printed successfully", vbInformation Also, check that no Excel instance is left open after running the script. _______________________________________________ dba-Tech mailing list dba-Tech at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-tech Website: http://www.databaseadvisors.com From gustav at cactus.dk Sat Jun 22 02:16:37 2019 From: gustav at cactus.dk (Gustav Brock) Date: Sat, 22 Jun 2019 07:16:37 +0000 Subject: [dba-Tech] VBS question In-Reply-To: <00bb01d52879$ea6b92d0$bf42b870$@gmail.com> References: , <00bb01d52879$ea6b92d0$bf42b870$@gmail.com> Message-ID: Hi Susan 1. Shouldn't happen, but easy to check 2. Use: objwb.Close False /gustav ________________________________ Fra: dba-Tech p? vegne af Susan Harkins Sendt: 21. juni 2019 23:40 Til: 'Discussion of Hardware and Software issues' Emne: Re: [dba-Tech] VBS question It's working now. I had a misnamed variable (ugh). I hate that kind of problem -- hard to find yourself. I left it and planted flowers in the garden I maintain as volunteer. Came back and spotted it right away. I have two more questions though: 1.) I don't want to close all instances of Excel, just the one that's running the macro. I don't want to inadvertently shut someone down who might be using Excel. 2.) I want to inhibit the Excel Save when exiting prompt. Should I do this in the Excel procedure or in the VBS script? Thanks everyone for your help today. Susan H. Hi Susan It could be that it doesn't run using your account. Try moving the script and workbook to the Shared/Public Documents folder. /gustav -----Oprindelig meddelelse----- Fra: dba-Tech P? vegne af Susan Harkins Sendt: 21. juni 2019 16:01 Til: 'Discussion of Hardware and Software issues' Emne: Re: [dba-Tech] VBS question Thanks Gustav -- still not working. I dropped in a cell(1,"A").Value = Time() statement just test and it doesn't work either -- the script is running -- I can see the Echo on the screen. Not sure how to continue troubleshooting. Is it possible that it's something with my Task Scheduler settings? The Action is Start a program. The Program/script is C:\Windows\Systems32\cscript.exe. The only argment is "C:\Users\Susan Harkins\Documents\PrintPivotTable.vbs" I have the visible property set to True and I thought I would see Excel quickly open, but that doesn't happen. Should it? Susan H. tech at databaseadvisors.com> Subject: Re: [dba-Tech] VBS question Hi Susan Excel is very picky with its objects. So, try: '.vbs file to print Excel PivoTable1.xlsm at 8am daily. 'Path to workbook. strPath = "C:\Documents\PivotTable1.xlsm" 'Macro name. strMacro = "PrintUpdatedPivotTable" 'Create an Excel instance. Set objApp = CreateObject("Excel.Application") Set objwb = objExcel.Workbooks.Open(strPath) objApp.Visible = True ' Should not be needed. objApp.Run strMacro objwb.Close Set objwb = Nothing objApp.Quit Set objApp = Nothing 'Scheduled task completed. MsgBox strPath & " " & strMacro & " PivotTable printed successfully", vbInformation Also, check that no Excel instance is left open after running the script. From ssharkins at gmail.com Sat Jun 22 07:46:20 2019 From: ssharkins at gmail.com (Susan Harkins) Date: Sat, 22 Jun 2019 08:46:20 -0400 Subject: [dba-Tech] VBS question In-Reply-To: References: , <00bb01d52879$ea6b92d0$bf42b870$@gmail.com> Message-ID: <00c601d528f8$7f695e70$7e3c1b50$@gmail.com> Thanks Gustav -- you're right about 1) -- easy to check and as you suggest, might not be necessary. Susan H. Hi Susan 1. Shouldn't happen, but easy to check 2. Use: objwb.Close False /gustav ________________________________ Fra: dba-Tech p? vegne af Susan Harkins Sendt: 21. juni 2019 23:40 Til: 'Discussion of Hardware and Software issues' Emne: Re: [dba-Tech] VBS question It's working now. I had a misnamed variable (ugh). I hate that kind of problem -- hard to find yourself. I left it and planted flowers in the garden I maintain as volunteer. Came back and spotted it right away. I have two more questions though: 1.) I don't want to close all instances of Excel, just the one that's running the macro. I don't want to inadvertently shut someone down who might be using Excel. 2.) I want to inhibit the Excel Save when exiting prompt. Should I do this in the Excel procedure or in the VBS script? Thanks everyone for your help today. Susan H. Hi Susan It could be that it doesn't run using your account. Try moving the script and workbook to the Shared/Public Documents folder. /gustav -----Oprindelig meddelelse----- Fra: dba-Tech P? vegne af Susan Harkins Sendt: 21. juni 2019 16:01 Til: 'Discussion of Hardware and Software issues' Emne: Re: [dba-Tech] VBS question Thanks Gustav -- still not working. I dropped in a cell(1,"A").Value = Time() statement just test and it doesn't work either -- the script is running -- I can see the Echo on the screen. Not sure how to continue troubleshooting. Is it possible that it's something with my Task Scheduler settings? The Action is Start a program. The Program/script is C:\Windows\Systems32\cscript.exe. The only argment is "C:\Users\Susan Harkins\Documents\PrintPivotTable.vbs" I have the visible property set to True and I thought I would see Excel quickly open, but that doesn't happen. Should it? Susan H. tech at databaseadvisors.com> Subject: Re: [dba-Tech] VBS question Hi Susan Excel is very picky with its objects. So, try: '.vbs file to print Excel PivoTable1.xlsm at 8am daily. 'Path to workbook. strPath = "C:\Documents\PivotTable1.xlsm" 'Macro name. strMacro = "PrintUpdatedPivotTable" 'Create an Excel instance. Set objApp = CreateObject("Excel.Application") Set objwb = objExcel.Workbooks.Open(strPath) objApp.Visible = True ' Should not be needed. objApp.Run strMacro objwb.Close Set objwb = Nothing objApp.Quit Set objApp = Nothing 'Scheduled task completed. MsgBox strPath & " " & strMacro & " PivotTable printed successfully", vbInformation Also, check that no Excel instance is left open after running the script. _______________________________________________ dba-Tech mailing list dba-Tech at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-tech Website: http://www.databaseadvisors.com From ssharkins at gmail.com Sat Jun 22 11:25:16 2019 From: ssharkins at gmail.com (Susan Harkins) Date: Sat, 22 Jun 2019 12:25:16 -0400 Subject: [dba-Tech] VBS question In-Reply-To: References: , <00bb01d52879$ea6b92d0$bf42b870$@gmail.com> Message-ID: <004101d52917$13ef8ab0$3bcea010$@gmail.com> Working right as rain this morning. Even startled me a bit when the printer kicked in. ? Thanks everyone! Susan H. Hi Susan 1. Shouldn't happen, but easy to check 2. Use: objwb.Close False /gustav From jbartow at winhaven.net Mon Jun 24 17:38:52 2019 From: jbartow at winhaven.net (John Bartow) Date: Mon, 24 Jun 2019 22:38:52 +0000 Subject: [dba-Tech] Introducing Azure SQL Database Edge Message-ID: Thought maybe some of you may be interested in this: https://info.microsoft.com/ww-landing-introducing-azure-sql-database-edge.html?lcid=en-us&ocid=mkto_eml_EM559704A1LA1 From rockysmolin at bchacc.com Mon Jun 24 23:45:21 2019 From: rockysmolin at bchacc.com (Rocky Smolin) Date: Mon, 24 Jun 2019 21:45:21 -0700 Subject: [dba-Tech] Adobe ID Message-ID: <006f01d52b10$cbc90e40$635b2ac0$@bchacc.com> Does anyone know what version of Photoshop and/or Adobe Premier Elements was the first to require an Adobe ID and online authorization? MTIA Rocky Smolin Beach Access Software 760-683-5777 www.bchacc.com www.e-z-mrp.com Skype: rocky.smolin