From bensonforums at gmail.com  Sun Jul  5 21:48:34 2020
From: bensonforums at gmail.com (Bill Benson)
Date: Sun, 5 Jul 2020 22:48:34 -0400
Subject: [AccessD] Access 365 and Azure - DateTime fields
In-Reply-To: <002b01d64bff$70b4f760$521ee620$@dalyn.co.nz>
References: <00bb01d64914$a76ab490$f6401db0$@dalyn.co.nz>
	<5EF1AF85.16578.4AD63AA@stuart.lexacorp.com.pg>
	<5EF1B080.7052.4B13A98@stuart.lexacorp.com.pg>
	<010e01d64933$2f5b9860$8e12c920$@dalyn.co.nz>
	<001601d64b2e$d740df20$85c29d60$@dalyn.co.nz>
	<CALGJE96CRcY2_EYrzk7yEGBbXCxGeJ07a3ZVXr3DY6wWrMV1SQ@mail.gmail.com>
	<002b01d64bff$70b4f760$521ee620$@dalyn.co.nz>
Message-ID: <CAJLzs_2JiBF+T_ZkcmYU992-OwTBVu64DdHe=3zE6g66rXC_yw@mail.gmail.com>

David,

Not sure how you tested (so I guess I am asking what you did). I think if I
were trying to test this, I would create a routine that ran the same query
using that SQL for a few minutes to see if I got any illogical entries. Did
you do something similar?

On Fri, Jun 26, 2020 at 5:20 PM David Emerson <newsgrps at dalyn.co.nz> wrote:

> The code is mostly part of a multiple insert line so using a variable to
> store the date won't work in this instance.
>
> I did a bit of testing and the clock flipping didn't seem to be an issue.
>
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> Paul Hartland via AccessD
> Sent: Friday, 26 June 2020 4:46 p.m.
> To: Access Developers discussion and problem solving
> Cc: Paul Hartland
> Subject: Re: [AccessD] Access 365 and Azure - DateTime fields
>
> I may of gone a slightly different route, instead of :
> DATEADD(ms, -DATEPART(ms, GETDATE()), GETDATE())
> I would of probably done this
> declare @dtMyDate as datetime
> set @dtmydate = getdate()
> set @mydate = dateadd(ms,-(dateadd(ms,-(), @mydate) ), @mydate)
>
> Paul
>
> On Thu, 25 Jun 2020, 21:26 David Emerson, <newsgrps at dalyn.co.nz> wrote:
>
> > I solved this one by removing the milliseconds this way:
> >
> > DATEADD(ms, -DATEPART(ms, GETDATE()), GETDATE())
> >
> > Thanks for the ideas.
> >
> > David
> >
> > -----Original Message-----
> > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> > David Emerson
> > Sent: Tuesday, 23 June 2020 7:52 p.m.
> > To: 'Access Developers discussion and problem solving'
> > Subject: Re: [AccessD] Access 365 and Azure - DateTime fields
> >
> > Previously I have had problems with Datetime2 not working with Access.
> > Have
> > things changed?
> >
> > -----Original Message-----
> > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> > Stuart McLachlan
> > Sent: Tuesday, 23 June 2020 7:34 p.m.
> > To: Access Developers discussion and problem solving
> > Subject: Re: [AccessD] Access 365 and Azure - DateTime fields
> >
> > Correction!  Datetime2 is 100 nanosecond precision, not icrosecond!
> >
> > On 23 Jun 2020 at 17:30, Stuart McLachlan wrote:
> >
> > > Try changing the  field to datetime2.
> > >
> > > https://docs.microsoft.com/en-us/sql/t-sql/data-types/datetime-transac
> > > t-sql?view=sql-server-v er15 <quote> DateTime.... Use the time, date,
> > > datetime2 and datetimeoffset data types for new work. These types
> > > align with the SQL Standard. They are more portable. time, datetime2
> > > and datetimeoffset provide more seconds precision. </quote>
> > >
> > > Sounds like the driver is trying to write a DateTime2 (microsecoonds)
> > > compatible value to a parameter bound to a  DateTime (milliseconds)
> > > field.
> > >
> > >
> > > On 23 Jun 2020 at 16:13, David Emerson wrote:
> > >
> > > > Hi Listers,
> > > >
> > > >
> > > >
> > > > Another problem with the conversion from SQL 2008 to Azure L
> > > >
> > > >
> > > >
> > > > When saving a record with a date field in it I am getting an error
> > > > "[Microsoft][ODBC Driver 17 for SQL Server]Datetime field overflow.
> > > > Fractional second precision exceeds the scale specified in the
> > > > parameter binding."
> > > >
> > > >
> > > >
> > > > What confuses me is that the record already has the date fields
> > > > filled in and saved.  All I am changing is a text field.
> > > >
> > > >
> > > >
> > > > I am using ADO to get the recordset for the form.  The SQL table
> > > > date fields are datetime SQL data type to match the Access date data
> > > > type.
> > > >
> > > >
> > > >
> > > > This article came the closest to having useful information but I am
> > > > not sure how to set the number of decimal digits.
> > > >
> > > >
> > > >
> > > > http://rightondevelopment.blogspot.com/2009/10/sql-server-native-cli
> > > > en t-100- datetime.html
> > > >
> > > >
> > > >
> > > > Can anyone steer me in the right direction?
> > > >
> > > >
> > > >
> > > > Regards
> > > >
> > > > David Emerson
> > > > Dalyn Software Ltd
> > > > Wellington, New Zealand
> >
> > --
> > 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
>

From bensonforums at gmail.com  Sun Jul  5 21:49:39 2020
From: bensonforums at gmail.com (Bill Benson)
Date: Sun, 5 Jul 2020 22:49:39 -0400
Subject: [AccessD] Access 365 and Azure - DateTime fields
In-Reply-To: <CAJLzs_2JiBF+T_ZkcmYU992-OwTBVu64DdHe=3zE6g66rXC_yw@mail.gmail.com>
References: <00bb01d64914$a76ab490$f6401db0$@dalyn.co.nz>
	<5EF1AF85.16578.4AD63AA@stuart.lexacorp.com.pg>
	<5EF1B080.7052.4B13A98@stuart.lexacorp.com.pg>
	<010e01d64933$2f5b9860$8e12c920$@dalyn.co.nz>
	<001601d64b2e$d740df20$85c29d60$@dalyn.co.nz>
	<CALGJE96CRcY2_EYrzk7yEGBbXCxGeJ07a3ZVXr3DY6wWrMV1SQ@mail.gmail.com>
	<002b01d64bff$70b4f760$521ee620$@dalyn.co.nz>
	<CAJLzs_2JiBF+T_ZkcmYU992-OwTBVu64DdHe=3zE6g66rXC_yw@mail.gmail.com>
Message-ID: <CAJLzs_2bZOj9-rcKbPwGk-VUnUcHgDxForQCxxULN-5rW9zv=w@mail.gmail.com>

Poor Paul, he has been getting duplicate posts since June 26. Not sure why
we are using Reply-All as a reflex nowadays  :)

On Sun, Jul 5, 2020 at 10:48 PM Bill Benson <bensonforums at gmail.com> wrote:

> David,
>
> Not sure how you tested (so I guess I am asking what you did). I think if
> I were trying to test this, I would create a routine that ran the same
> query using that SQL for a few minutes to see if I got any illogical
> entries. Did you do something similar?
>
> On Fri, Jun 26, 2020 at 5:20 PM David Emerson <newsgrps at dalyn.co.nz>
> wrote:
>
>> The code is mostly part of a multiple insert line so using a variable to
>> store the date won't work in this instance.
>>
>> I did a bit of testing and the clock flipping didn't seem to be an issue.
>>
>> -----Original Message-----
>> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
>> Paul Hartland via AccessD
>> Sent: Friday, 26 June 2020 4:46 p.m.
>> To: Access Developers discussion and problem solving
>> Cc: Paul Hartland
>> Subject: Re: [AccessD] Access 365 and Azure - DateTime fields
>>
>> I may of gone a slightly different route, instead of :
>> DATEADD(ms, -DATEPART(ms, GETDATE()), GETDATE())
>> I would of probably done this
>> declare @dtMyDate as datetime
>> set @dtmydate = getdate()
>> set @mydate = dateadd(ms,-(dateadd(ms,-(), @mydate) ), @mydate)
>>
>> Paul
>>
>> On Thu, 25 Jun 2020, 21:26 David Emerson, <newsgrps at dalyn.co.nz> wrote:
>>
>> > I solved this one by removing the milliseconds this way:
>> >
>> > DATEADD(ms, -DATEPART(ms, GETDATE()), GETDATE())
>> >
>> > Thanks for the ideas.
>> >
>> > David
>> >
>> > -----Original Message-----
>> > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf
>> Of
>> > David Emerson
>> > Sent: Tuesday, 23 June 2020 7:52 p.m.
>> > To: 'Access Developers discussion and problem solving'
>> > Subject: Re: [AccessD] Access 365 and Azure - DateTime fields
>> >
>> > Previously I have had problems with Datetime2 not working with Access.
>> > Have
>> > things changed?
>> >
>> > -----Original Message-----
>> > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf
>> Of
>> > Stuart McLachlan
>> > Sent: Tuesday, 23 June 2020 7:34 p.m.
>> > To: Access Developers discussion and problem solving
>> > Subject: Re: [AccessD] Access 365 and Azure - DateTime fields
>> >
>> > Correction!  Datetime2 is 100 nanosecond precision, not icrosecond!
>> >
>> > On 23 Jun 2020 at 17:30, Stuart McLachlan wrote:
>> >
>> > > Try changing the  field to datetime2.
>> > >
>> > >
>> https://docs.microsoft.com/en-us/sql/t-sql/data-types/datetime-transac
>> > > t-sql?view=sql-server-v er15 <quote> DateTime.... Use the time, date,
>> > > datetime2 and datetimeoffset data types for new work. These types
>> > > align with the SQL Standard. They are more portable. time, datetime2
>> > > and datetimeoffset provide more seconds precision. </quote>
>> > >
>> > > Sounds like the driver is trying to write a DateTime2 (microsecoonds)
>> > > compatible value to a parameter bound to a  DateTime (milliseconds)
>> > > field.
>> > >
>> > >
>> > > On 23 Jun 2020 at 16:13, David Emerson wrote:
>> > >
>> > > > Hi Listers,
>> > > >
>> > > >
>> > > >
>> > > > Another problem with the conversion from SQL 2008 to Azure L
>> > > >
>> > > >
>> > > >
>> > > > When saving a record with a date field in it I am getting an error
>> > > > "[Microsoft][ODBC Driver 17 for SQL Server]Datetime field overflow.
>> > > > Fractional second precision exceeds the scale specified in the
>> > > > parameter binding."
>> > > >
>> > > >
>> > > >
>> > > > What confuses me is that the record already has the date fields
>> > > > filled in and saved.  All I am changing is a text field.
>> > > >
>> > > >
>> > > >
>> > > > I am using ADO to get the recordset for the form.  The SQL table
>> > > > date fields are datetime SQL data type to match the Access date data
>> > > > type.
>> > > >
>> > > >
>> > > >
>> > > > This article came the closest to having useful information but I am
>> > > > not sure how to set the number of decimal digits.
>> > > >
>> > > >
>> > > >
>> > > >
>> http://rightondevelopment.blogspot.com/2009/10/sql-server-native-cli
>> > > > en t-100- datetime.html
>> > > >
>> > > >
>> > > >
>> > > > Can anyone steer me in the right direction?
>> > > >
>> > > >
>> > > >
>> > > > Regards
>> > > >
>> > > > David Emerson
>> > > > Dalyn Software Ltd
>> > > > Wellington, New Zealand
>> >
>> > --
>> > 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
>>
>

From newsgrps at dalyn.co.nz  Sun Jul  5 22:19:12 2020
From: newsgrps at dalyn.co.nz (David Emerson)
Date: Mon, 6 Jul 2020 15:19:12 +1200
Subject: [AccessD] Access 365 and Azure - DateTime fields
In-Reply-To: <CAJLzs_2JiBF+T_ZkcmYU992-OwTBVu64DdHe=3zE6g66rXC_yw@mail.gmail.com>
References: <00bb01d64914$a76ab490$f6401db0$@dalyn.co.nz>	<5EF1AF85.16578.4AD63AA@stuart.lexacorp.com.pg>	<5EF1B080.7052.4B13A98@stuart.lexacorp.com.pg>	<010e01d64933$2f5b9860$8e12c920$@dalyn.co.nz>	<001601d64b2e$d740df20$85c29d60$@dalyn.co.nz>	<CALGJE96CRcY2_EYrzk7yEGBbXCxGeJ07a3ZVXr3DY6wWrMV1SQ@mail.gmail.com>	<002b01d64bff$70b4f760$521ee620$@dalyn.co.nz>
	<CAJLzs_2JiBF+T_ZkcmYU992-OwTBVu64DdHe=3zE6g66rXC_yw@mail.gmail.com>
Message-ID: <004a01d65344$3a502220$aef06660$@dalyn.co.nz>

Hi Paul,

I had a table of over 36k records.  I ran some code to update them all and
didn't seem to have any problems.

As a check I will be looking at the tables this week to see that the new
records are all as expected.

Regards, David

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Bill Benson
Sent: Monday, 6 July 2020 2:49 p.m.
To: Access Developers discussion and problem solving
Cc: Paul Hartland
Subject: Re: [AccessD] Access 365 and Azure - DateTime fields

David,

Not sure how you tested (so I guess I am asking what you did). I think if I
were trying to test this, I would create a routine that ran the same query
using that SQL for a few minutes to see if I got any illogical entries. Did
you do something similar?

On Fri, Jun 26, 2020 at 5:20 PM David Emerson <newsgrps at dalyn.co.nz> wrote:

> The code is mostly part of a multiple insert line so using a variable to
> store the date won't work in this instance.
>
> I did a bit of testing and the clock flipping didn't seem to be an issue.
>
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> Paul Hartland via AccessD
> Sent: Friday, 26 June 2020 4:46 p.m.
> To: Access Developers discussion and problem solving
> Cc: Paul Hartland
> Subject: Re: [AccessD] Access 365 and Azure - DateTime fields
>
> I may of gone a slightly different route, instead of :
> DATEADD(ms, -DATEPART(ms, GETDATE()), GETDATE())
> I would of probably done this
> declare @dtMyDate as datetime
> set @dtmydate = getdate()
> set @mydate = dateadd(ms,-(dateadd(ms,-(), @mydate) ), @mydate)
>
> Paul
>
> On Thu, 25 Jun 2020, 21:26 David Emerson, <newsgrps at dalyn.co.nz> wrote:
>
> > I solved this one by removing the milliseconds this way:
> >
> > DATEADD(ms, -DATEPART(ms, GETDATE()), GETDATE())
> >
> > Thanks for the ideas.
> >
> > David
> >
> > -----Original Message-----
> > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> > David Emerson
> > Sent: Tuesday, 23 June 2020 7:52 p.m.
> > To: 'Access Developers discussion and problem solving'
> > Subject: Re: [AccessD] Access 365 and Azure - DateTime fields
> >
> > Previously I have had problems with Datetime2 not working with Access.
> > Have
> > things changed?
> >
> > -----Original Message-----
> > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> > Stuart McLachlan
> > Sent: Tuesday, 23 June 2020 7:34 p.m.
> > To: Access Developers discussion and problem solving
> > Subject: Re: [AccessD] Access 365 and Azure - DateTime fields
> >
> > Correction!  Datetime2 is 100 nanosecond precision, not icrosecond!
> >
> > On 23 Jun 2020 at 17:30, Stuart McLachlan wrote:
> >
> > > Try changing the  field to datetime2.
> > >
> > > https://docs.microsoft.com/en-us/sql/t-sql/data-types/datetime-transac
> > > t-sql?view=sql-server-v er15 <quote> DateTime.... Use the time, date,
> > > datetime2 and datetimeoffset data types for new work. These types
> > > align with the SQL Standard. They are more portable. time, datetime2
> > > and datetimeoffset provide more seconds precision. </quote>
> > >
> > > Sounds like the driver is trying to write a DateTime2 (microsecoonds)
> > > compatible value to a parameter bound to a  DateTime (milliseconds)
> > > field.
> > >
> > >
> > > On 23 Jun 2020 at 16:13, David Emerson wrote:
> > >
> > > > Hi Listers,
> > > >
> > > >
> > > >
> > > > Another problem with the conversion from SQL 2008 to Azure L
> > > >
> > > >
> > > >
> > > > When saving a record with a date field in it I am getting an error
> > > > "[Microsoft][ODBC Driver 17 for SQL Server]Datetime field overflow.
> > > > Fractional second precision exceeds the scale specified in the
> > > > parameter binding."
> > > >
> > > >
> > > >
> > > > What confuses me is that the record already has the date fields
> > > > filled in and saved.  All I am changing is a text field.
> > > >
> > > >
> > > >
> > > > I am using ADO to get the recordset for the form.  The SQL table
> > > > date fields are datetime SQL data type to match the Access date data
> > > > type.
> > > >
> > > >
> > > >
> > > > This article came the closest to having useful information but I am
> > > > not sure how to set the number of decimal digits.
> > > >
> > > >
> > > >
> > > > http://rightondevelopment.blogspot.com/2009/10/sql-server-native-cli
> > > > en t-100- datetime.html
> > > >
> > > >
> > > >
> > > > Can anyone steer me in the right direction?
> > > >
> > > >
> > > >
> > > > Regards
> > > >
> > > > David Emerson
> > > > Dalyn Software Ltd
> > > > Wellington, New Zealand


From newsgrps at dalyn.co.nz  Tue Jul  7 01:41:41 2020
From: newsgrps at dalyn.co.nz (David Emerson)
Date: Tue, 7 Jul 2020 18:41:41 +1200
Subject: [AccessD] Finding and Installing SQL Drivers
Message-ID: <00aa01d65429$af6c7000$0e455000$@dalyn.co.nz>

Hi Team,

 

I asked a client what ODBC drivers they have installed on their RDS
computers.  They found none on either when they looked in the Programs and
Features section of the Control Panel.

 

I have two connection strings that work:

 

gADODBConnection.ConnectionString = "Provider=sqloledb;Data
Source=NZS00SQL1;Initial Catalog=StockData5;Integrated Security=SSPI;"

 

qdefTemp.Connect = "ODBC;DRIVER=SQL
Server;SERVER=NZS00SQL1;DATABASE=StockData5;Trusted_Connection=Yes"

 

I have a few  questions:

 

What is the driver that they are using?

 

Where would it be installed?

 

I am also wanting to update the drivers to the latest ones - I am guessing
that it should it be installed on the computer running the Access program
and not the computer hosting the SQL server.  Is this correct?

 

Regards

David Emerson
Dalyn Software Ltd
Wellington, New Zealand

 

 

 


From stuart at lexacorp.com.pg  Tue Jul  7 02:34:45 2020
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Tue, 07 Jul 2020 17:34:45 +1000
Subject: [AccessD] Finding and Installing SQL Drivers
In-Reply-To: <00aa01d65429$af6c7000$0e455000$@dalyn.co.nz>
References: <00aa01d65429$af6c7000$0e455000$@dalyn.co.nz>
Message-ID: <5F042595.5545.1615A2@stuart.lexacorp.com.pg>

Programs & Feature will only show drivers that have been installed as standalone 
installations. It won't tell you what drivers have been installed by a package such as MS 
Office.

A better place to look is under the Drivers tab in the two  odbcad32.exe applications
which you will find in ..\ system32\ (for 64 bit drivers) and ..\SysWow64\ (for 32bit drivers)

That will tell you the version numbers and DLL names of all of the  installed drivers.

> gADODBConnection.ConnectionString = "Provider=sqloledb;Data
> Source=NZS00SQL1;Initial Catalog=StockData5;Integrated Security=SSPI;"

That would be sqloledb.dll,
 probably in C:\Program Files (x86)\Common Files\System\Ole DB for the  32 bit driver
and C:\Program Files\Common Files\System\Ole DB for 64 bit

> qdefTemp.Connect = "ODBC;DRIVER=SQL
> Server;SERVER=NZS00SQL1;DATABASE=StockData5;Trusted_Connection=Yes"

That's probably MSODBCSQL.xx.dll  in system32 and sysWOW4 for the 64/32 bit drivers.
(where xx is the version number)

Yes, the driver needs to be installed on the machine running the application

On 7 Jul 2020 at 18:41, David Emerson wrote:

> Hi Team,
> 
> 
> 
> I asked a client what ODBC drivers they have installed on their RDS
> computers.  They found none on either when they looked in the Programs
> and Features section of the Control Panel.
> 
> 
> 
> I have two connection strings that work:
> 
> 
> 
> gADODBConnection.ConnectionString = "Provider=sqloledb;Data
> Source=NZS00SQL1;Initial Catalog=StockData5;Integrated Security=SSPI;"
> 
> 
> 
> qdefTemp.Connect = "ODBC;DRIVER=SQL
> Server;SERVER=NZS00SQL1;DATABASE=StockData5;Trusted_Connection=Yes"
> 
> 
> 
> I have a few  questions:
> 
> 
> 
> What is the driver that they are using?
> 
> 
> 
> Where would it be installed?
> 
> 
> 
> I am also wanting to update the drivers to the latest ones - I am
> guessing that it should it be installed on the computer running the
> Access program and not the computer hosting the SQL server.  Is this
> correct?
> 
> 
> 
> Regards
> 
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand


From stuart at lexacorp.com.pg  Tue Jul  7 02:39:16 2020
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Tue, 07 Jul 2020 17:39:16 +1000
Subject: [AccessD] Finding and Installing SQL Drivers
In-Reply-To: <00aa01d65429$af6c7000$0e455000$@dalyn.co.nz>
References: <00aa01d65429$af6c7000$0e455000$@dalyn.co.nz>
Message-ID: <5F0426A4.9527.1A3BD7@stuart.lexacorp.com.pg>


Programs & Feature will only show drivers that have been installed as standalone 
installations. It won't tell you what drivers have been installed by a package such as MS 
Office.

A better place to look is under the Drivers tab in the two? odbcad32.exe applications
which you will find in ..\ system32\ (for 64 bit drivers) and ..\SysWow64\ (for 32bit drivers)

That will tell you the version numbers and DLL names of all of the? installed drivers.

>gADODBConnection.ConnectionString = "Provider=sqloledb;Data
> Source=NZS00SQL1;Initial Catalog=StockData5;Integrated Security=SSPI;"

That would be sqloledb.dll,
?probably in C:\Program Files (x86)\Common Files\System\Ole DB for the? 32 bit driver
and C:\Program Files\Common Files\System\Ole DB for 64 bit

> qdefTemp.Connect = "ODBC;DRIVER=SQL
>Server;SERVER=NZS00SQL1;DATABASE=StockData5;Trusted_Connection=Yes"

That's probably MSODBCSQL.xx.dll? in system32 and sysWOW4 for the 64/32 bit drivers.
(where xx is the version number)

Yes, the driver needs to be installed on the machine running the application

On 7 Jul 2020 at 18:41, David Emerson wrote:

> Hi Team,
>
>
>
> I asked a client what ODBC drivers they have installed on their RDS
> computers.? They found none on either when they looked in the Programs
> and Features section of the Control Panel.
>
>
>
> I have two connection strings that work:
>
>
>
>gADODBConnection.ConnectionString = "Provider=sqloledb;Data
> Source=NZS00SQL1;Initial Catalog=StockData5;Integrated Security=SSPI;"
>
>
>
> qdefTemp.Connect = "ODBC;DRIVER=SQL
>Server;SERVER=NZS00SQL1;DATABASE=StockData5;Trusted_Connection=Yes"
>
>
>
> I have a few? questions:
>
>
>
> What is the driver that they are using?
>
>
>
> Where would it be installed?
>
>
>
> I am also wanting to update the drivers to the latest ones - I am
> guessing that it should it be installed on the computer running the
> Access program and not the computer hosting the SQL server.? Is this
> correct?
>
>
>
> Regards
>
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand
??



From newsgrps at dalyn.co.nz  Tue Jul  7 03:13:18 2020
From: newsgrps at dalyn.co.nz (David Emerson)
Date: Tue, 7 Jul 2020 20:13:18 +1200
Subject: [AccessD] Finding and Installing SQL Drivers
In-Reply-To: <5F042595.5545.1615A2@stuart.lexacorp.com.pg>
References: <00aa01d65429$af6c7000$0e455000$@dalyn.co.nz>
	<5F042595.5545.1615A2@stuart.lexacorp.com.pg>
Message-ID: <00b401d65436$7b4f73a0$71ee5ae0$@dalyn.co.nz>

Thanks Stuart.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Stuart McLachlan
Sent: Tuesday, 7 July 2020 7:35 p.m.
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Finding and Installing SQL Drivers

Programs & Feature will only show drivers that have been installed as
standalone 
installations. It won't tell you what drivers have been installed by a
package such as MS 
Office.

A better place to look is under the Drivers tab in the two  odbcad32.exe
applications
which you will find in ..\ system32\ (for 64 bit drivers) and ..\SysWow64\
(for 32bit drivers)

That will tell you the version numbers and DLL names of all of the
installed drivers.

> gADODBConnection.ConnectionString = "Provider=sqloledb;Data
> Source=NZS00SQL1;Initial Catalog=StockData5;Integrated Security=SSPI;"

That would be sqloledb.dll,
 probably in C:\Program Files (x86)\Common Files\System\Ole DB for the  32
bit driver
and C:\Program Files\Common Files\System\Ole DB for 64 bit

> qdefTemp.Connect = "ODBC;DRIVER=SQL
> Server;SERVER=NZS00SQL1;DATABASE=StockData5;Trusted_Connection=Yes"

That's probably MSODBCSQL.xx.dll  in system32 and sysWOW4 for the 64/32 bit
drivers.
(where xx is the version number)

Yes, the driver needs to be installed on the machine running the application

On 7 Jul 2020 at 18:41, David Emerson wrote:

> Hi Team,
> 
> 
> 
> I asked a client what ODBC drivers they have installed on their RDS
> computers.  They found none on either when they looked in the Programs
> and Features section of the Control Panel.
> 
> 
> 
> I have two connection strings that work:
> 
> 
> 
> gADODBConnection.ConnectionString = "Provider=sqloledb;Data
> Source=NZS00SQL1;Initial Catalog=StockData5;Integrated Security=SSPI;"
> 
> 
> 
> qdefTemp.Connect = "ODBC;DRIVER=SQL
> Server;SERVER=NZS00SQL1;DATABASE=StockData5;Trusted_Connection=Yes"
> 
> 
> 
> I have a few  questions:
> 
> 
> 
> What is the driver that they are using?
> 
> 
> 
> Where would it be installed?
> 
> 
> 
> I am also wanting to update the drivers to the latest ones - I am
> guessing that it should it be installed on the computer running the
> Access program and not the computer hosting the SQL server.  Is this
> correct?
> 
> 
> 
> Regards
> 
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand

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


From paul.hartland at googlemail.com  Wed Jul 15 05:01:46 2020
From: paul.hartland at googlemail.com (Paul Hartland)
Date: Wed, 15 Jul 2020 11:01:46 +0100
Subject: [AccessD] MS Office 2019 Professional Plus
Message-ID: <CALGJE97iGxhs3W3k2pdonzLtQtX5kPwp9YwrrVu5cCTi2QkH5w@mail.gmail.com>

To all,

Not purchased a copy of Microsoft Office in a long time, If I was to buy
the 2019 Professional plus edition will that allow me to issue runtime
versions of the software I develop using it, or do I need some sort of
developer edition ?

Thanks in advance for any help :)

-- 
Paul Hartland
paul.hartland at googlemail.com

From gustav at cactus.dk  Wed Jul 15 05:08:57 2020
From: gustav at cactus.dk (Gustav Brock)
Date: Wed, 15 Jul 2020 10:08:57 +0000
Subject: [AccessD] MS Office 2019 Professional Plus
Message-ID: <HE1PR10MB1692171A58F85AB60E64C128CA7E0@HE1PR10MB1692.EURPRD10.PROD.OUTLOOK.COM>

Hi Paul

The runtime (any version since A2007) is a separate free download. Nothing more is needed,

/gustav

-----Oprindelig meddelelse-----
Fra: AccessD <accessd-bounces at databaseadvisors.com> P? vegne af Paul Hartland via AccessD
Sendt: 15. juli 2020 12:02
Til: Access List <accessd at databaseadvisors.com>
Cc: Paul Hartland <paul.hartland at googlemail.com>
Emne: [AccessD] MS Office 2019 Professional Plus

To all,

Not purchased a copy of Microsoft Office in a long time, If I was to buy the 2019 Professional plus edition will that allow me to issue runtime versions of the software I develop using it, or do I need some sort of developer edition ?

Thanks in advance for any help :)

--
Paul Hartland
paul.hartland at googlemail.com
-- 


From paul.hartland at googlemail.com  Wed Jul 15 05:12:21 2020
From: paul.hartland at googlemail.com (Paul Hartland)
Date: Wed, 15 Jul 2020 11:12:21 +0100
Subject: [AccessD] MS Office 2019 Professional Plus
In-Reply-To: <HE1PR10MB1692171A58F85AB60E64C128CA7E0@HE1PR10MB1692.EURPRD10.PROD.OUTLOOK.COM>
References: <HE1PR10MB1692171A58F85AB60E64C128CA7E0@HE1PR10MB1692.EURPRD10.PROD.OUTLOOK.COM>
Message-ID: <CALGJE94css-Zbj6CG=yiPsNWgZSet8ZJxJVOBhB+CrkP4nZDew@mail.gmail.com>

Ah thank you, will look for that later.

Paul

On Wed, 15 Jul 2020, 11:09 Gustav Brock via AccessD, <
accessd at databaseadvisors.com> wrote:

> Hi Paul
>
> The runtime (any version since A2007) is a separate free download. Nothing
> more is needed,
>
> /gustav
>
> -----Oprindelig meddelelse-----
> Fra: AccessD <accessd-bounces at databaseadvisors.com> P? vegne af Paul
> Hartland via AccessD
> Sendt: 15. juli 2020 12:02
> Til: Access List <accessd at databaseadvisors.com>
> Cc: Paul Hartland <paul.hartland at googlemail.com>
> Emne: [AccessD] MS Office 2019 Professional Plus
>
> To all,
>
> Not purchased a copy of Microsoft Office in a long time, If I was to buy
> the 2019 Professional plus edition will that allow me to issue runtime
> versions of the software I develop using it, or do I need some sort of
> developer edition ?
>
> Thanks in advance for any help :)
>
> --
> Paul Hartland
> paul.hartland at googlemail.com
> --
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From jwcolby at gmail.com  Fri Jul 31 13:55:46 2020
From: jwcolby at gmail.com (John Colby)
Date: Fri, 31 Jul 2020 14:55:46 -0400
Subject: [AccessD] Can anyone help me?
Message-ID: <CAA_iUE_Mw6jW7VM_pg-rx=mORMZ9H3_RJvMzzuZW1JJAyEuf0w@mail.gmail.com>

I wrote a framework back in the day.  It resides in an Access library and I
no longer have Access installed.  Or any other Microsoft Office program for
that matter.  I remember that you could export modules (and classes) to
text files.  This was used under versions up to 2007 IIRC.

Is anyone able to (and know how to) take my library MDA, export everything,
and zip the files and send them to me?  I'd like to place them on GIT as
public code, as a demo of what i have done, albeit in the past.

If you are able to do this, please email me and I will send a copy of the
MDA.

TIA

John W. Colby

-- 
John W. Colby
Colby Consulting

From df.waters at outlook.com  Fri Jul 31 14:09:15 2020
From: df.waters at outlook.com (Daniel Waters)
Date: Fri, 31 Jul 2020 19:09:15 +0000
Subject: [AccessD] Can anyone help me?
In-Reply-To: <CAA_iUE_Mw6jW7VM_pg-rx=mORMZ9H3_RJvMzzuZW1JJAyEuf0w@mail.gmail.com>
References: <CAA_iUE_Mw6jW7VM_pg-rx=mORMZ9H3_RJvMzzuZW1JJAyEuf0w@mail.gmail.com>
Message-ID: <DM6PR05MB69225019B4B419387A2BE655F64E0@DM6PR05MB6922.namprd05.prod.outlook.com>

Hi John,

I wrote a small Access App which can do that.  Send me your Access App and I'll send back the text files!  Shouldn't take long.

Dan
df.waters at outlook.com


-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John Colby
Sent: Friday, July 31, 2020 1:56 PM
To: Access Developers discussion and problem solving
Subject: [AccessD] Can anyone help me?

I wrote a framework back in the day.  It resides in an Access library and I
no longer have Access installed.  Or any other Microsoft Office program for
that matter.  I remember that you could export modules (and classes) to
text files.  This was used under versions up to 2007 IIRC.

Is anyone able to (and know how to) take my library MDA, export everything,
and zip the files and send them to me?  I'd like to place them on GIT as
public code, as a demo of what i have done, albeit in the past.

If you are able to do this, please email me and I will send a copy of the
MDA.

TIA

John W. Colby

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