From mar.ko at verizon.net  Thu Oct  3 14:48:04 2019
From: mar.ko at verizon.net (Mark Simms)
Date: Thu, 3 Oct 2019 19:48:04 +0000 (UTC)
Subject: [AccessD] Windows 2010 corruption issue: A Thanks to all
References: <1212941053.3241993.1570132084530.ref@mail.yahoo.com>
Message-ID: <1212941053.3241993.1570132084530@mail.yahoo.com>

I just wanted to thank everyone who contributed to the issue of Windows 2010 database corruption issue.The suggested registry changes did the trick. I implemented the fix via Powershell.
Most importantly, I just got paid by my client. As a result of this, my client updated all of their workstations to Windows 2010.This was just awesome.
Thanks again to all that helped.,
Mark Simms
marksimms at verizon.net


From jackandpat.d at gmail.com  Thu Oct  3 16:25:21 2019
From: jackandpat.d at gmail.com (jack drawbridge)
Date: Thu, 3 Oct 2019 17:25:21 -0400
Subject: [AccessD] Windows 2010 corruption issue: A Thanks to all
In-Reply-To: <1212941053.3241993.1570132084530@mail.yahoo.com>
References: <1212941053.3241993.1570132084530.ref@mail.yahoo.com>
	<1212941053.3241993.1570132084530@mail.yahoo.com>
Message-ID: <CAKvidAtx3SRmXgSi6v23MCahRtFT9JUn40-K6_9yvtjfd2A20g@mail.gmail.com>

Congrats Mark!

On Thu, Oct 3, 2019 at 3:49 PM Mark Simms via AccessD <
accessd at databaseadvisors.com> wrote:

> I just wanted to thank everyone who contributed to the issue of Windows
> 2010 database corruption issue.The suggested registry changes did the
> trick. I implemented the fix via Powershell.
> Most importantly, I just got paid by my client. As a result of this, my
> client updated all of their workstations to Windows 2010.This was just
> awesome.
> Thanks again to all that helped.,
> Mark Simms
> marksimms at verizon.net
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From accessd at shaw.ca  Thu Oct  3 17:31:33 2019
From: accessd at shaw.ca (Jim Lawrence)
Date: Thu, 3 Oct 2019 16:31:33 -0600 (MDT)
Subject: [AccessD] Windows 2010 corruption issue: A Thanks to all
In-Reply-To: <1212941053.3241993.1570132084530@mail.yahoo.com>
References: <1212941053.3241993.1570132084530.ref@mail.yahoo.com>
	<1212941053.3241993.1570132084530@mail.yahoo.com>
Message-ID: <1200751295.387237270.1570141893165.JavaMail.zimbra@shaw.ca>

Could you please post the method you used as I somehow lost much of the previous conversation. 

Jim

----- Original Message -----
From: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com>
To: "Access Developers discussion and problem solving" <accessd at databaseadvisors.com>
Cc: "Mark Simms" <mar.ko at verizon.net>
Sent: Thursday, October 3, 2019 12:48:04 PM
Subject: [AccessD] Windows 2010 corruption issue: A Thanks to all

I just wanted to thank everyone who contributed to the issue of Windows 2010 database corruption issue.The suggested registry changes did the trick. I implemented the fix via Powershell.
Most importantly, I just got paid by my client. As a result of this, my client updated all of their workstations to Windows 2010.This was just awesome.
Thanks again to all that helped.,
Mark Simms
marksimms at verizon.net

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

From jwcolby at gmail.com  Mon Oct  7 10:56:04 2019
From: jwcolby at gmail.com (John Colby)
Date: Mon, 7 Oct 2019 11:56:04 -0400
Subject: [AccessD] Windows 2010 corruption issue: A Thanks to all
In-Reply-To: <1212941053.3241993.1570132084530@mail.yahoo.com>
References: <1212941053.3241993.1570132084530.ref@mail.yahoo.com>
	<1212941053.3241993.1570132084530@mail.yahoo.com>
Message-ID: <CAA_iUE9UfQ3s_e4OfdqY9jfLAjbftcv9F+hG6=i9Wq-ZCfwqHA@mail.gmail.com>

congrats on getting paid! :)

On Thu, Oct 3, 2019 at 3:49 PM Mark Simms via AccessD <
accessd at databaseadvisors.com> wrote:

> I just wanted to thank everyone who contributed to the issue of Windows
> 2010 database corruption issue.The suggested registry changes did the
> trick. I implemented the fix via Powershell.
> Most importantly, I just got paid by my client. As a result of this, my
> client updated all of their workstations to Windows 2010.This was just
> awesome.
> Thanks again to all that helped.,
> Mark Simms
> marksimms at verizon.net
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
John W. Colby
Colby Consulting

From Chester_Kaup at kindermorgan.com  Tue Oct  8 15:23:53 2019
From: Chester_Kaup at kindermorgan.com (Kaup, Chester)
Date: Tue, 8 Oct 2019 20:23:53 +0000
Subject: [AccessD] Query trouble
Message-ID: <8E16E03987F1FD4FB0A9BEBF7CC160CBB58BE8FF@HOUEX11.kindermorgan.com>

I am trying to use both a not like and not equal statement in the same query. Either criteria work correctly by itself. When I use both nothing is excluded. What might I be doing wrong? Below is the SQL statement. Thanks.

SELECT dbo_DSS_LastStatus.PID, dbo_DSS_LastStatus.Completion_Name, dbo_DSS_LastStatus.Status, [tbl Petra Current Status Copy].[Sym Code] INTO [tbl Petra and DSS Status]
FROM (dbo_DSS_LastStatus INNER JOIN dbo_DSS_CompletionMaster ON dbo_DSS_LastStatus.PID = dbo_DSS_CompletionMaster.PID) INNER JOIN [tbl Petra Current Status Copy] ON dbo_DSS_CompletionMaster.ParentPID = [tbl Petra Current Status Copy].[UWI (APINum)]
GROUP BY dbo_DSS_LastStatus.PID, dbo_DSS_LastStatus.Completion_Name, dbo_DSS_LastStatus.Status, [tbl Petra Current Status Copy].[Sym Code]
HAVING ((([tbl Petra Current Status Copy].[Sym Code]) Not Like "PA*")) OR ((([tbl Petra Current Status Copy].[Sym Code])<>"P&A"));

From wrwehler at gmail.com  Tue Oct  8 15:51:42 2019
From: wrwehler at gmail.com (Ryan W)
Date: Tue, 8 Oct 2019 15:51:42 -0500
Subject: [AccessD] Query trouble
In-Reply-To: <8E16E03987F1FD4FB0A9BEBF7CC160CBB58BE8FF@HOUEX11.kindermorgan.com>
References: <8E16E03987F1FD4FB0A9BEBF7CC160CBB58BE8FF@HOUEX11.kindermorgan.com>
Message-ID: <1A10F7C0-A3DC-4404-A5EA-8E97E79F30FC@gmail.com>

You want AND between your criteria, not OR I believe. 

Sent from my iPhone

> On Oct 8, 2019, at 3:24 PM, Kaup, Chester <Chester_Kaup at kindermorgan.com> wrote:
> 
> ?I am trying to use both a not like and not equal statement in the same query. Either criteria work correctly by itself. When I use both nothing is excluded. What might I be doing wrong? Below is the SQL statement. Thanks.
> 
> SELECT dbo_DSS_LastStatus.PID, dbo_DSS_LastStatus.Completion_Name, dbo_DSS_LastStatus.Status, [tbl Petra Current Status Copy].[Sym Code] INTO [tbl Petra and DSS Status]
> FROM (dbo_DSS_LastStatus INNER JOIN dbo_DSS_CompletionMaster ON dbo_DSS_LastStatus.PID = dbo_DSS_CompletionMaster.PID) INNER JOIN [tbl Petra Current Status Copy] ON dbo_DSS_CompletionMaster.ParentPID = [tbl Petra Current Status Copy].[UWI (APINum)]
> GROUP BY dbo_DSS_LastStatus.PID, dbo_DSS_LastStatus.Completion_Name, dbo_DSS_LastStatus.Status, [tbl Petra Current Status Copy].[Sym Code]
> HAVING ((([tbl Petra Current Status Copy].[Sym Code]) Not Like "PA*")) OR ((([tbl Petra Current Status Copy].[Sym Code])<>"P&A"));
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com


From stuart at lexacorp.com.pg  Tue Oct  8 15:59:48 2019
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Wed, 09 Oct 2019 06:59:48 +1000
Subject: [AccessD] Query trouble
In-Reply-To: <8E16E03987F1FD4FB0A9BEBF7CC160CBB58BE8FF@HOUEX11.kindermorgan.com>
References: <8E16E03987F1FD4FB0A9BEBF7CC160CBB58BE8FF@HOUEX11.kindermorgan.com>
Message-ID: <5D9CF8C4.27211.27460DE3@stuart.lexacorp.com.pg>

The coun of yoour  opening and closing parentheses don't match


On 8 Oct 2019 at 20:23, Kaup, Chester wrote:

> HAVING ((([tbl Petra Current Status
> Copy].[Sym Code]) Not Like "PA*")) OR ((([tbl Petra Current Status
> Copy].[Sym Code])<>"P&A"))



From Chester_Kaup at kindermorgan.com  Tue Oct  8 16:04:10 2019
From: Chester_Kaup at kindermorgan.com (Kaup, Chester)
Date: Tue, 8 Oct 2019 21:04:10 +0000
Subject: [AccessD] Query trouble
In-Reply-To: <1A10F7C0-A3DC-4404-A5EA-8E97E79F30FC@gmail.com>
References: <8E16E03987F1FD4FB0A9BEBF7CC160CBB58BE8FF@HOUEX11.kindermorgan.com>
	<1A10F7C0-A3DC-4404-A5EA-8E97E79F30FC@gmail.com>
Message-ID: <8E16E03987F1FD4FB0A9BEBF7CC160CBB58BE93F@HOUEX11.kindermorgan.com>

Perfect. Thank you.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Ryan W
Sent: Tuesday, October 08, 2019 3:52 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Query trouble

[This email message was received from the Internet and came from outside of Kinder Morgan]


You want AND between your criteria, not OR I believe. 

Sent from my iPhone

> On Oct 8, 2019, at 3:24 PM, Kaup, Chester <Chester_Kaup at kindermorgan.com> wrote:
> 
> ?I am trying to use both a not like and not equal statement in the same query. Either criteria work correctly by itself. When I use both nothing is excluded. What might I be doing wrong? Below is the SQL statement. Thanks.
> 
> SELECT dbo_DSS_LastStatus.PID, dbo_DSS_LastStatus.Completion_Name, dbo_DSS_LastStatus.Status, [tbl Petra Current Status Copy].[Sym Code] INTO [tbl Petra and DSS Status]
> FROM (dbo_DSS_LastStatus INNER JOIN dbo_DSS_CompletionMaster ON dbo_DSS_LastStatus.PID = dbo_DSS_CompletionMaster.PID) INNER JOIN [tbl Petra Current Status Copy] ON dbo_DSS_CompletionMaster.ParentPID = [tbl Petra Current Status Copy].[UWI (APINum)]
> GROUP BY dbo_DSS_LastStatus.PID, dbo_DSS_LastStatus.Completion_Name, dbo_DSS_LastStatus.Status, [tbl Petra Current Status Copy].[Sym Code]
> HAVING ((([tbl Petra Current Status Copy].[Sym Code]) Not Like "PA*")) OR ((([tbl Petra Current Status Copy].[Sym Code])<>"P&A"));
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


From Chester_Kaup at kindermorgan.com  Wed Oct  9 09:05:36 2019
From: Chester_Kaup at kindermorgan.com (Kaup, Chester)
Date: Wed, 9 Oct 2019 14:05:36 +0000
Subject: [AccessD] Add criteria to query
Message-ID: <8E16E03987F1FD4FB0A9BEBF7CC160CBB58BEC95@HOUEX11.kindermorgan.com>

I have the following query that works fine. Thanks to some help from people here.

SELECT dbo_DSS_LastStatus.PID, dbo_DSS_LastStatus.Completion_Name, dbo_DSS_LastStatus.Status, [tbl Petra Current Status Copy].[Sym Code]
INTO [tbl Petra and DSS Status]
FROM (dbo_DSS_LastStatus INNER JOIN dbo_DSS_CompletionMaster ON dbo_DSS_LastStatus.PID = dbo_DSS_CompletionMaster.PID)
INNER JOIN [tbl Petra Current Status Copy] ON dbo_DSS_CompletionMaster.ParentPID = [tbl Petra Current Status Copy].[UWI (APINum)]
GROUP BY dbo_DSS_LastStatus.PID, dbo_DSS_LastStatus.Completion_Name, dbo_DSS_LastStatus.Status, [tbl Petra Current Status Copy].[Sym Code]
HAVING ((([tbl Petra Current Status Copy].[Sym Code]) Not Like "PA*" And ([tbl Petra Current Status Copy].[Sym Code])<>"P&A" And ([tbl Petra Current Status Copy].[Sym Code])<>"side"));

I then added criteria for Sym Code of  "infill". The issue is all records of Sym Code "infill" are being returned. Your assistance appreciated.

SELECT dbo_DSS_LastStatus.PID, dbo_DSS_LastStatus.Completion_Name, dbo_DSS_LastStatus.Status, [tbl Petra Current Status Copy].[Sym Code] INTO [tbl Petra and DSS Status]
FROM (dbo_DSS_LastStatus INNER JOIN dbo_DSS_CompletionMaster ON dbo_DSS_LastStatus.PID = dbo_DSS_CompletionMaster.PID) INNER JOIN [tbl Petra Current Status Copy] ON dbo_DSS_CompletionMaster.ParentPID = [tbl Petra Current Status Copy].[UWI (APINum)]
GROUP BY dbo_DSS_LastStatus.PID, dbo_DSS_LastStatus.Completion_Name, dbo_DSS_LastStatus.Status, [tbl Petra Current Status Copy].[Sym Code]
HAVING ((([tbl Petra Current Status Copy].[Sym Code]) Not Like "PA*" And ([tbl Petra Current Status Copy].[Sym Code])<>"P&A" And ([tbl Petra Current Status Copy].[Sym Code])<>"side")) OR (((dbo_DSS_LastStatus.Status)="TA" Or (dbo_DSS_LastStatus.Status)="P&A") AND (([tbl Petra Current Status Copy].[Sym Code])="infill"));


From stuart at lexacorp.com.pg  Wed Oct  9 16:48:39 2019
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Thu, 10 Oct 2019 07:48:39 +1000
Subject: [AccessD] Add criteria to query
In-Reply-To: <8E16E03987F1FD4FB0A9BEBF7CC160CBB58BEC95@HOUEX11.kindermorgan.com>
References: <8E16E03987F1FD4FB0A9BEBF7CC160CBB58BEC95@HOUEX11.kindermorgan.com>
Message-ID: <5D9E55B7.4431.2C99242D@stuart.lexacorp.com.pg>

>  I then added criteria for Sym Code of  "infill". The issue is all records
of Sym Code "infill" are being returned. Your assistance appreciated.

If you split your SQL into lines and ident on brackets it makes it much easier to identify the 
problems caused by incorrect bracketing of complex conditions:

The "infill" condition is only being applied to the Last_Status condition inside the outer "OR"
If the first half of the condition is met, the "infill" condition is not tested.


HAVING 
(
	(
		([tbl Petra Current Status Copy].[Sym Code]) Not Like "PA*" 
		And 
		([tbl Petra Current Status Copy].[Sym Code])<>"P&A"
		And 
		([tbl Petra Current Status Copy].[Sym Code])<>"side"
	)
)

OR 

(
	(
		(dbo_DSS_LastStatus.Status)="TA" 
		Or
		(dbo_DSS_LastStatus.Status)="P&A"
	) 
		AND 
		(
			([tbl Petra Current Status Copy].[Sym Code])="infill"
		)
);





On 9 Oct 2019 at 14:05, Kaup, Chester wrote:

> SELECT dbo_DSS_LastStatus.PID, dbo_DSS_LastStatus.Completion_Name,
> dbo_DSS_LastStatus.Status, [tbl Petra Current Status Copy].[Sym Code]
> INTO [tbl Petra and DSS Status] FROM (dbo_DSS_LastStatus INNER JOIN
> dbo_DSS_CompletionMaster ON dbo_DSS_LastStatus.PID =
> dbo_DSS_CompletionMaster.PID) INNER JOIN [tbl Petra Current Status
> Copy] ON dbo_DSS_CompletionMaster.ParentPID = [tbl Petra Current
> Status Copy].[UWI (APINum)] GROUP BY dbo_DSS_LastStatus.PID,
> dbo_DSS_LastStatus.Completion_Name, dbo_DSS_LastStatus.Status, [tbl
> Petra Current Status Copy].[Sym Code] HAVING ((([tbl Petra Current
> Status Copy].[Sym Code]) Not Like "PA*" And ([tbl Petra Current Status
> Copy].[Sym Code])<>"P&A" And ([tbl Petra Current Status Copy].[Sym
> Code])<>"side")) OR (((dbo_DSS_LastStatus.Status)="TA" Or
> (dbo_DSS_LastStatus.Status)="P&A") AND (([tbl Petra Current Status
> Copy].[Sym Code])="infill"));



From Chester_Kaup at kindermorgan.com  Thu Oct 10 09:14:21 2019
From: Chester_Kaup at kindermorgan.com (Kaup, Chester)
Date: Thu, 10 Oct 2019 14:14:21 +0000
Subject: [AccessD] Add criteria to query
In-Reply-To: <5D9E55B7.4431.2C99242D@stuart.lexacorp.com.pg>
References: <8E16E03987F1FD4FB0A9BEBF7CC160CBB58BEC95@HOUEX11.kindermorgan.com>
	<5D9E55B7.4431.2C99242D@stuart.lexacorp.com.pg>
Message-ID: <8E16E03987F1FD4FB0A9BEBF7CC160CBB58C146B@HOUEX11.kindermorgan.com>

Good point. Better than what I tried in the past with using color.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan
Sent: Wednesday, October 09, 2019 4:49 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Add criteria to query

[This email message was received from the Internet and came from outside of Kinder Morgan]


>  I then added criteria for Sym Code of  "infill". The issue is all records
of Sym Code "infill" are being returned. Your assistance appreciated.

If you split your SQL into lines and ident on brackets it makes it much easier to identify the 
problems caused by incorrect bracketing of complex conditions:

The "infill" condition is only being applied to the Last_Status condition inside the outer "OR"
If the first half of the condition is met, the "infill" condition is not tested.


HAVING 
(
	(
		([tbl Petra Current Status Copy].[Sym Code]) Not Like "PA*" 
		And 
		([tbl Petra Current Status Copy].[Sym Code])<>"P&A"
		And 
		([tbl Petra Current Status Copy].[Sym Code])<>"side"
	)
)

OR 

(
	(
		(dbo_DSS_LastStatus.Status)="TA" 
		Or
		(dbo_DSS_LastStatus.Status)="P&A"
	) 
		AND 
		(
			([tbl Petra Current Status Copy].[Sym Code])="infill"
		)
);





On 9 Oct 2019 at 14:05, Kaup, Chester wrote:

> SELECT dbo_DSS_LastStatus.PID, dbo_DSS_LastStatus.Completion_Name,
> dbo_DSS_LastStatus.Status, [tbl Petra Current Status Copy].[Sym Code]
> INTO [tbl Petra and DSS Status] FROM (dbo_DSS_LastStatus INNER JOIN
> dbo_DSS_CompletionMaster ON dbo_DSS_LastStatus.PID =
> dbo_DSS_CompletionMaster.PID) INNER JOIN [tbl Petra Current Status
> Copy] ON dbo_DSS_CompletionMaster.ParentPID = [tbl Petra Current
> Status Copy].[UWI (APINum)] GROUP BY dbo_DSS_LastStatus.PID,
> dbo_DSS_LastStatus.Completion_Name, dbo_DSS_LastStatus.Status, [tbl
> Petra Current Status Copy].[Sym Code] HAVING ((([tbl Petra Current
> Status Copy].[Sym Code]) Not Like "PA*" And ([tbl Petra Current Status
> Copy].[Sym Code])<>"P&A" And ([tbl Petra Current Status Copy].[Sym
> Code])<>"side")) OR (((dbo_DSS_LastStatus.Status)="TA" Or
> (dbo_DSS_LastStatus.Status)="P&A") AND (([tbl Petra Current Status
> Copy].[Sym Code])="infill"));


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com



From jackandpat.d at gmail.com  Thu Oct 31 07:45:03 2019
From: jackandpat.d at gmail.com (jack drawbridge)
Date: Thu, 31 Oct 2019 08:45:03 -0400
Subject: [AccessD] Interesting Access article
Message-ID: <CAKvidAuHKm8kuh5A6KKtnwMmwaTfhO1G=ZVQyeiTkFt=roM4fg@mail.gmail.com>

Just saw this discussed on a few forums.
Interesting article on Access's continued survival.
<https://medium.com/young-coder/microsoft-access-the-zombie-database-software-that-wont-die-5b09e389c166>
jack

From stuart at lexacorp.com.pg  Thu Oct 31 08:27:18 2019
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Thu, 31 Oct 2019 23:27:18 +1000
Subject: [AccessD] Interesting Access article
In-Reply-To: <CAKvidAuHKm8kuh5A6KKtnwMmwaTfhO1G=ZVQyeiTkFt=roM4fg@mail.gmail.com>
References: <CAKvidAuHKm8kuh5A6KKtnwMmwaTfhO1G=ZVQyeiTkFt=roM4fg@mail.gmail.com>
Message-ID: <5DBAE136.31507.64E5D412@stuart.lexacorp.com.pg>

He has missed the point entirely.

Access is not a database!

Access is a very powerful Rapid Application Development environment which can use its own 
native database format (Microsoft Jet) or any number of  robust  RDBMSs.
 
The statement "These statistics almost certainly overstate the popularity of Access" is 100% 
wrong.   A number of those Oracle, SQL Server and MySQL segments of the pie chart will be 
using Access as an application FE.

I've been building complex Access applications using SQL Server and MySQL as the 
database for years.


On 31 Oct 2019 at 8:45, jack drawbridge wrote:

> Just saw this discussed on a few forums.
> Interesting article on Access's continued survival.
> <https://medium.com/young-coder/microsoft-access-the-zombie-database-s
> oftware-that-wont-die-5b09e389c166> jack -- AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd Website:
> http://www.databaseadvisors.com
> 



From wrwehler at gmail.com  Thu Oct 31 08:38:46 2019
From: wrwehler at gmail.com (Ryan W)
Date: Thu, 31 Oct 2019 08:38:46 -0500
Subject: [AccessD] Interesting Access article
In-Reply-To: <5DBAE136.31507.64E5D412@stuart.lexacorp.com.pg>
References: <CAKvidAuHKm8kuh5A6KKtnwMmwaTfhO1G=ZVQyeiTkFt=roM4fg@mail.gmail.com>
	<5DBAE136.31507.64E5D412@stuart.lexacorp.com.pg>
Message-ID: <CAFXiSd_NZAp3Z+dNdV5hEhvVdo=_4z_YTPV9Gk=2Gg68Zje5hw@mail.gmail.com>

Absolutely.  Nothing else that I've tried compares.  Have you ever tried to
make a datasheet object in JAVA? Last I tried you had to bind the
datasource to the datasheet, which I think they call a JTABLE and then you
can't even really manipulate the data within it without a bunch more
code/logic.  Access is completely magical in so many regards... I wish
Microsoft take it more seriously.



On Thu, Oct 31, 2019 at 8:28 AM Stuart McLachlan <stuart at lexacorp.com.pg>
wrote:

> He has missed the point entirely.
>
> Access is not a database!
>
> Access is a very powerful Rapid Application Development environment which
> can use its own
> native database format (Microsoft Jet) or any number of  robust  RDBMSs.
>
> The statement "These statistics almost certainly overstate the popularity
> of Access" is 100%
> wrong.   A number of those Oracle, SQL Server and MySQL segments of the
> pie chart will be
> using Access as an application FE.
>
> I've been building complex Access applications using SQL Server and MySQL
> as the
> database for years.
>
>
> On 31 Oct 2019 at 8:45, jack drawbridge wrote:
>
> > Just saw this discussed on a few forums.
> > Interesting article on Access's continued survival.
> > <https://medium.com/young-coder/microsoft-access-the-zombie-database-s
> > oftware-that-wont-die-5b09e389c166> jack -- AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd Website:
> > http://www.databaseadvisors.com
> >
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From df.waters at outlook.com  Thu Oct 31 09:46:05 2019
From: df.waters at outlook.com (Daniel Waters)
Date: Thu, 31 Oct 2019 14:46:05 +0000
Subject: [AccessD] Interesting Access article
In-Reply-To: <CAKvidAuHKm8kuh5A6KKtnwMmwaTfhO1G=ZVQyeiTkFt=roM4fg@mail.gmail.com>
References: <CAKvidAuHKm8kuh5A6KKtnwMmwaTfhO1G=ZVQyeiTkFt=roM4fg@mail.gmail.com>
Message-ID: <DM6PR05MB59293C8EFD47FD25CECD57BAF6630@DM6PR05MB5929.namprd05.prod.outlook.com>

Interesting, but mostly negative article.  What I liked was that most of the replies were quite positive about Access.  I wrote a reply which I hope will add to a positive impression of Access.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of jack drawbridge
Sent: October 31, 2019 7:45
To: Access Developers discussion and problem solving
Subject: [AccessD] Interesting Access article

Just saw this discussed on a few forums.
Interesting article on Access's continued survival.
<https://medium.com/young-coder/microsoft-access-the-zombie-database-software-that-wont-die-5b09e389c166>
jack
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


From jackandpat.d at gmail.com  Thu Oct 31 10:21:31 2019
From: jackandpat.d at gmail.com (jack drawbridge)
Date: Thu, 31 Oct 2019 11:21:31 -0400
Subject: [AccessD] Interesting Access article
In-Reply-To: <DM6PR05MB59293C8EFD47FD25CECD57BAF6630@DM6PR05MB5929.namprd05.prod.outlook.com>
References: <CAKvidAuHKm8kuh5A6KKtnwMmwaTfhO1G=ZVQyeiTkFt=roM4fg@mail.gmail.com>
	<DM6PR05MB59293C8EFD47FD25CECD57BAF6630@DM6PR05MB5929.namprd05.prod.outlook.com>
Message-ID: <CAKvidAuvOO8c=hW3eNk4T5UUS+rKaKCfzb8YhWxBn5vGFi75qA@mail.gmail.com>

Good write up Dan. The author seems focused on the DB part and not the
RAD/FE to anything aspect.  He's quite negative. Glad to see some responses
enumerating the  ease of use and complementary nature of Access for "quick
and easy access" to other database software applications.

On Thu, Oct 31, 2019 at 10:46 AM Daniel Waters <df.waters at outlook.com>
wrote:

> Interesting, but mostly negative article.  What I liked was that most of
> the replies were quite positive about Access.  I wrote a reply which I hope
> will add to a positive impression of Access.
>
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> jack drawbridge
> Sent: October 31, 2019 7:45
> To: Access Developers discussion and problem solving
> Subject: [AccessD] Interesting Access article
>
> Just saw this discussed on a few forums.
> Interesting article on Access's continued survival.
> <
> https://medium.com/young-coder/microsoft-access-the-zombie-database-software-that-wont-die-5b09e389c166
> >
> jack
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From fuller.artful at gmail.com  Thu Oct 31 16:58:20 2019
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Thu, 31 Oct 2019 17:58:20 -0400
Subject: [AccessD] Interesting Access article
In-Reply-To: <CAKvidAuvOO8c=hW3eNk4T5UUS+rKaKCfzb8YhWxBn5vGFi75qA@mail.gmail.com>
References: <CAKvidAuHKm8kuh5A6KKtnwMmwaTfhO1G=ZVQyeiTkFt=roM4fg@mail.gmail.com>
	<DM6PR05MB59293C8EFD47FD25CECD57BAF6630@DM6PR05MB5929.namprd05.prod.outlook.com>
	<CAKvidAuvOO8c=hW3eNk4T5UUS+rKaKCfzb8YhWxBn5vGFi75qA@mail.gmail.com>
Message-ID: <CAEPJO1gSMfgwsDSAax0hODSHRxOnOwgxwbhFiJq4_NWTi0_NOQ@mail.gmail.com>

I have written more than a few enterprise-side apps using Access and
Termiinal Server About 100 users at once, give or take a dozen, people from
all the North American time-zones.
Access is an awesome tool, and I think maybe more powerful than MS
consented to. I used to write monolithic apps that did everything, but
subsequently learned another way to skin the apple, as it were: write each
task as a  separate app; create shortcuts to them all; one double-click
executes the task and then exits. The whole point of this is to eliminate
the user, which most obviously works for Reports. Double-click this button
and magically the report spits out of your printer, or perhaps a text file.
No fuss, no muss; there it is.

On Thu, Oct 31, 2019 at 11:22 AM jack drawbridge <jackandpat.d at gmail.com>
wrote:

> Good write up Dan. The author seems focused on the DB part and not the
> RAD/FE to anything aspect.  He's quite negative. Glad to see some responses
> enumerating the  ease of use and complementary nature of Access for "quick
> and easy access" to other database software applications.
>
> On Thu, Oct 31, 2019 at 10:46 AM Daniel Waters <df.waters at outlook.com>
> wrote:
>
> > Interesting, but mostly negative article.  What I liked was that most of
> > the replies were quite positive about Access.  I wrote a reply which I
> hope
> > will add to a positive impression of Access.
> >
> > -----Original Message-----
> > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> > jack drawbridge
> > Sent: October 31, 2019 7:45
> > To: Access Developers discussion and problem solving
> > Subject: [AccessD] Interesting Access article
> >
> > Just saw this discussed on a few forums.
> > Interesting article on Access's continued survival.
> > <
> >
> https://medium.com/young-coder/microsoft-access-the-zombie-database-software-that-wont-die-5b09e389c166
> > >
> > jack
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
Arthur