From rockysmolin2 at gmail.com Wed Jun 17 22:43:18 2020 From: rockysmolin2 at gmail.com (rocky smolin) Date: Wed, 17 Jun 2020 20:43:18 -0700 Subject: [AccessD] Word Automation Message-ID: <015201d64522$9bca9d80$d35fd880$@gmail.com> Dear List: This is a word automation problem in reverse. Instead of pushing data onto a word form, the user , using a form they've used for a long time, wants the Access DB to get the info from the word form. Their process is that the person taking an order fills out the form, prints it and passes it to the person entering it into the DB. (Yes, I know they shouldn't do it that way.) The form already had text form fields for all the fields which I bookmarked to the fields in a table. The problem is that when one of the fields has data entered into it. The bookmark disappears, so that when my program tries to find the bookmark to get the data in the document's field, the bookmark is missing. Which means I'm also missing something. How can one preserve the bookmark after data has been entered into the document's field? MTIA Rocky Smolin Beach Access Software 760-683-5777 Please note new email address: rockysmolin2 at gmail.com From pcs.accessd at gmail.com Wed Jun 17 23:25:14 2020 From: pcs.accessd at gmail.com (Borge Hansen) Date: Thu, 18 Jun 2020 14:25:14 +1000 Subject: [AccessD] Word Automation In-Reply-To: <015201d64522$9bca9d80$d35fd880$@gmail.com> References: <015201d64522$9bca9d80$d35fd880$@gmail.com> Message-ID: Rocky, I think the issue as you describe it is dealt with here: https://wordribbon.tips.net/T007875_Protecting_Bookmarks /borge On Thu, 18 Jun 2020 at 1:43 pm, rocky smolin wrote: > > > Dear List: > This is a word automation problem in reverse. Instead of pushing data onto > a word form, the user , using a form they've used for a long time, wants the > Access DB to get the info from the word form. > > Their process is that the person taking an order fills out the form, prints > it and passes it to the person entering it into the DB. (Yes, I know they > shouldn't do it that way.) > The form already had text form fields for all the fields which I bookmarked > to the fields in a table. > > The problem is that when one of the fields has data entered into it. The > bookmark disappears, so that when my program tries to find the bookmark to > get the data in the document's field, the bookmark is missing. > > Which means I'm also missing something. How can one preserve the bookmark > after data has been entered into the document's field? > > MTIA > Rocky Smolin > Beach Access Software > 760-683-5777 > Please note new email address: rockysmolin2 at gmail.com > From ssharkins at gmail.com Thu Jun 18 09:05:13 2020 From: ssharkins at gmail.com (Susan Harkins) Date: Thu, 18 Jun 2020 10:05:13 -0400 Subject: [AccessD] Word Automation In-Reply-To: References: <015201d64522$9bca9d80$d35fd880$@gmail.com> Message-ID: <024801d64579$7cf83910$76e8ab30$@gmail.com> I've worked with forms and Access before and I don't remember having this problem. I'm perplexed. I suppose Rocky, you could write a quick loop that resets all the bookmarks at the beginning of each entry session. Seems easier than trying to come up with a new strategy. Susan H. Rocky, I think the issue as you describe it is dealt with here: https://wordribbon.tips.net/T007875_Protecting_Bookmarks /borge On Thu, 18 Jun 2020 at 1:43 pm, rocky smolin wrote: > > > Dear List: > This is a word automation problem in reverse. Instead of pushing data > onto a word form, the user , using a form they've used for a long > time, wants the Access DB to get the info from the word form. > > Their process is that the person taking an order fills out the form, > prints it and passes it to the person entering it into the DB. (Yes, I > know they shouldn't do it that way.) The form already had text form > fields for all the fields which I bookmarked to the fields in a table. > > The problem is that when one of the fields has data entered into it. > The bookmark disappears, so that when my program tries to find the > bookmark to get the data in the document's field, the bookmark is missing. > > Which means I'm also missing something. How can one preserve the > bookmark after data has been entered into the document's field? > > MTIA > Rocky Smolin > Beach Access Software > 760-683-5777 > Please note new email address: rockysmolin2 at gmail.com > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com From John.Clark at niagaracounty.com Thu Jun 18 09:27:46 2020 From: John.Clark at niagaracounty.com (John W. Clark) Date: Thu, 18 Jun 2020 14:27:46 +0000 Subject: [AccessD] Word Automation In-Reply-To: <024801d64579$7cf83910$76e8ab30$@gmail.com> References: <015201d64522$9bca9d80$d35fd880$@gmail.com> , <024801d64579$7cf83910$76e8ab30$@gmail.com> Message-ID: Need help -- not in the Access game too much these days, but some of the old programs still haunt me from time to time. And that is the case now -- a program that was written 20 years ago is rearing it's ugly head. The program has been all but replaced but still holds a use as a "historical" lookup (it is a local resource for quick access to date for them). The recently had new PCs installed and are now on Windows 10 with, I believe Access 2016 (???). In any event I am trying to open this too, and I have 2016. Back when I used Access more, it would come up and ask if you wanted to update an older DB. I was hoping it did this, but it just says it cannot open it. Am I out of luck here? Thanks for any advice you can send my way -- even if it is bad news (at least I'll know where I stand) Notice: This electronic transmission is intended for the sole use of the individual or entity to which it is addressed and may contain confidential, privileged or otherwise legally protected information. If you are not the intended recipient, or if you believe you are not the intended recipient, you are hereby notified that any use, disclosure, copying, distribution, or the taking of any action in reliance on the contents of this information, is strictly prohibited. Niagara County is not responsible for the content of any external hyperlink referenced in this email or any email. IF YOU HAVE RECEIVED THIS TRANSMISSION IN ERROR, PLEASE NOTIFY THE SENDER IMMEDIATELY BY EMAIL AND DELETE THE ORIGINAL MESSAGE ALONG WITH ANY PAPER OR ELECTRONIC COPIES. Thank you for your cooperation. From John.Clark at niagaracounty.com Thu Jun 18 09:34:12 2020 From: John.Clark at niagaracounty.com (John W. Clark) Date: Thu, 18 Jun 2020 14:34:12 +0000 Subject: [AccessD] Help [WAS] Word Automation In-Reply-To: References: <015201d64522$9bca9d80$d35fd880$@gmail.com> , <024801d64579$7cf83910$76e8ab30$@gmail.com>, Message-ID: Sorry -- forgot to change the subject line ________________________________ From: AccessD on behalf of John W. Clark Sent: Thursday, June 18, 2020 10:27 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Word Automation [EXTERNAL MESSAGE] This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. - Niagara County IT Need help -- not in the Access game too much these days, but some of the old programs still haunt me from time to time. And that is the case now -- a program that was written 20 years ago is rearing it's ugly head. The program has been all but replaced but still holds a use as a "historical" lookup (it is a local resource for quick access to date for them). The recently had new PCs installed and are now on Windows 10 with, I believe Access 2016 (???). In any event I am trying to open this too, and I have 2016. Back when I used Access more, it would come up and ask if you wanted to update an older DB. I was hoping it did this, but it just says it cannot open it. Am I out of luck here? Thanks for any advice you can send my way -- even if it is bad news (at least I'll know where I stand) Notice: This electronic transmission is intended for the sole use of the individual or entity to which it is addressed and may contain confidential, privileged or otherwise legally protected information. If you are not the intended recipient, or if you believe you are not the intended recipient, you are hereby notified that any use, disclosure, copying, distribution, or the taking of any action in reliance on the contents of this information, is strictly prohibited. Niagara County is not responsible for the content of any external hyperlink referenced in this email or any email. IF YOU HAVE RECEIVED THIS TRANSMISSION IN ERROR, PLEASE NOTIFY THE SENDER IMMEDIATELY BY EMAIL AND DELETE THE ORIGINAL MESSAGE ALONG WITH ANY PAPER OR ELECTRONIC COPIES. Thank you for your cooperation. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com Notice: This electronic transmission is intended for the sole use of the individual or entity to which it is addressed and may contain confidential, privileged or otherwise legally protected information. If you are not the intended recipient, or if you believe you are not the intended recipient, you are hereby notified that any use, disclosure, copying, distribution, or the taking of any action in reliance on the contents of this information, is strictly prohibited. Niagara County is not responsible for the content of any external hyperlink referenced in this email or any email. IF YOU HAVE RECEIVED THIS TRANSMISSION IN ERROR, PLEASE NOTIFY THE SENDER IMMEDIATELY BY EMAIL AND DELETE THE ORIGINAL MESSAGE ALONG WITH ANY PAPER OR ELECTRONIC COPIES. Thank you for your cooperation. From gustav at cactus.dk Thu Jun 18 09:35:43 2020 From: gustav at cactus.dk (Gustav Brock) Date: Thu, 18 Jun 2020 14:35:43 +0000 Subject: [AccessD] Word Automation Message-ID: Hi John If 20 years old, it probably is of version Access 97. You will need Access 2000/2002/XP/2003 to open this and convert it to Access 2000+. That converted file you can open with Access 2007+ (and convert to the accdb format if you like). /gustav -----Oprindelig meddelelse----- Fra: AccessD P? vegne af John W. Clark Sendt: 18. juni 2020 16:28 Til: Access Developers discussion and problem solving Emne: Re: [AccessD] Word Automation Need help -- not in the Access game too much these days, but some of the old programs still haunt me from time to time. And that is the case now -- a program that was written 20 years ago is rearing it's ugly head. The program has been all but replaced but still holds a use as a "historical" lookup (it is a local resource for quick access to date for them). The recently had new PCs installed and are now on Windows 10 with, I believe Access 2016 (???). In any event I am trying to open this too, and I have 2016. Back when I used Access more, it would come up and ask if you wanted to update an older DB. I was hoping it did this, but it just says it cannot open it. Am I out of luck here? Thanks for any advice you can send my way -- even if it is bad news (at least I'll know where I stand) From rockysmolin2 at gmail.com Thu Jun 18 10:54:11 2020 From: rockysmolin2 at gmail.com (rocky smolin) Date: Thu, 18 Jun 2020 08:54:11 -0700 Subject: [AccessD] Word Automation In-Reply-To: <024801d64579$7cf83910$76e8ab30$@gmail.com> References: <015201d64522$9bca9d80$d35fd880$@gmail.com> <024801d64579$7cf83910$76e8ab30$@gmail.com> Message-ID: <015a01d64588$b6351810$229f4830$@gmail.com> I think I'm going to try to convince the client that this is bass-avkward. They should be doing the data entry in an Access form and THEN print out the work order if they need to. Now, they're filling out the word doc form, printing it, and entering that into the database. So the data is being entered twice. And I'm not sure what happens to the hard copy, but he told me they're not saving the word doc form under a unique identifier on the HD. r -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins Sent: Thursday, June 18, 2020 7:05 AM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Word Automation I've worked with forms and Access before and I don't remember having this problem. I'm perplexed. I suppose Rocky, you could write a quick loop that resets all the bookmarks at the beginning of each entry session. Seems easier than trying to come up with a new strategy. Susan H. Rocky, I think the issue as you describe it is dealt with here: https://wordribbon.tips.net/T007875_Protecting_Bookmarks /borge On Thu, 18 Jun 2020 at 1:43 pm, rocky smolin wrote: > > > Dear List: > This is a word automation problem in reverse. Instead of pushing data > onto a word form, the user , using a form they've used for a long > time, wants the Access DB to get the info from the word form. > > Their process is that the person taking an order fills out the form, > prints it and passes it to the person entering it into the DB. (Yes, I > know they shouldn't do it that way.) The form already had text form > fields for all the fields which I bookmarked to the fields in a table. > > The problem is that when one of the fields has data entered into it. > The bookmark disappears, so that when my program tries to find the > bookmark to get the data in the document's field, the bookmark is missing. > > Which means I'm also missing something. How can one preserve the > bookmark after data has been entered into the document's field? > > MTIA > Rocky Smolin > Beach Access Software > 760-683-5777 > Please note new email address: rockysmolin2 at gmail.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 rockysmolin2 at gmail.com Thu Jun 18 11:00:29 2020 From: rockysmolin2 at gmail.com (rocky smolin) Date: Thu, 18 Jun 2020 09:00:29 -0700 Subject: [AccessD] Word Automation In-Reply-To: References: <015201d64522$9bca9d80$d35fd880$@gmail.com> , <024801d64579$7cf83910$76e8ab30$@gmail.com> Message-ID: <015b01d64589$971ee9f0$c55cbdd0$@gmail.com> First I would verify that it does open in an older version. Then if possible try it in successively newer version to find out where it breaks. Is there no other error message or reason give, just 'cannot open'. Assuming it's still in good working order then it's got to be some incompatibility with the code or a reference. Can you open it without starting by holding the Shift key? If so then you could Alt-F11 into the code to see if it compiles. You could try the decompile from the Run box. Can you open a new database and import the objects from the old one? That's all the ideas I can think of in five minutes. :) Let us know the results. r -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John W. Clark Sent: Thursday, June 18, 2020 7:28 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Word Automation Need help -- not in the Access game too much these days, but some of the old programs still haunt me from time to time. And that is the case now -- a program that was written 20 years ago is rearing it's ugly head. The program has been all but replaced but still holds a use as a "historical" lookup (it is a local resource for quick access to date for them). The recently had new PCs installed and are now on Windows 10 with, I believe Access 2016 (???). In any event I am trying to open this too, and I have 2016. Back when I used Access more, it would come up and ask if you wanted to update an older DB. I was hoping it did this, but it just says it cannot open it. Am I out of luck here? Thanks for any advice you can send my way -- even if it is bad news (at least I'll know where I stand) Notice: This electronic transmission is intended for the sole use of the individual or entity to which it is addressed and may contain confidential, privileged or otherwise legally protected information. If you are not the intended recipient, or if you believe you are not the intended recipient, you are hereby notified that any use, disclosure, copying, distribution, or the taking of any action in reliance on the contents of this information, is strictly prohibited. Niagara County is not responsible for the content of any external hyperlink referenced in this email or any email. IF YOU HAVE RECEIVED THIS TRANSMISSION IN ERROR, PLEASE NOTIFY THE SENDER IMMEDIATELY BY EMAIL AND DELETE THE ORIGINAL MESSAGE ALONG WITH ANY PAPER OR ELECTRONIC COPIES. Thank you for your cooperation. -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com From jamesbutton at blueyonder.co.uk Thu Jun 18 11:41:59 2020 From: jamesbutton at blueyonder.co.uk (James Button) Date: Thu, 18 Jun 2020 17:41:59 +0100 Subject: [AccessD] Word Automation In-Reply-To: <015b01d64589$971ee9f0$c55cbdd0$@gmail.com> References: <015201d64522$9bca9d80$d35fd880$@gmail.com> , <024801d64579$7cf83910$76e8ab30$@gmail.com> <015b01d64589$971ee9f0$c55cbdd0$@gmail.com> Message-ID: Hi My PC has 2010 and 365 (family with Access) 365 on it will process a .mdb file - but that was updated to the new format (whatever) way back in 2016 Try File Options Default file format allows selection of 2000 2002~2003 or 2007~2016 You could also look at external data import for database And I have seen reference to a facility called "MDBopener.com" Or maybe try import (OK just the data!) into excel - Data >From Access Then again - maybe someone could convert the format for you if the data etc. is not confidential JimB -----Original Message----- From: AccessD On Behalf Of rocky smolin Sent: Thursday, June 18, 2020 5:00 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Word Automation First I would verify that it does open in an older version. Then if possible try it in successively newer version to find out where it breaks. Is there no other error message or reason give, just 'cannot open'. Assuming it's still in good working order then it's got to be some incompatibility with the code or a reference. Can you open it without starting by holding the Shift key? If so then you could Alt-F11 into the code to see if it compiles. You could try the decompile from the Run box. Can you open a new database and import the objects from the old one? That's all the ideas I can think of in five minutes. :) Let us know the results. r -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of John W. Clark Sent: Thursday, June 18, 2020 7:28 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Word Automation Need help -- not in the Access game too much these days, but some of the old programs still haunt me from time to time. And that is the case now -- a program that was written 20 years ago is rearing it's ugly head. The program has been all but replaced but still holds a use as a "historical" lookup (it is a local resource for quick access to date for them). The recently had new PCs installed and are now on Windows 10 with, I believe Access 2016 (???). In any event I am trying to open this too, and I have 2016. Back when I used Access more, it would come up and ask if you wanted to update an older DB. I was hoping it did this, but it just says it cannot open it. Am I out of luck here? Thanks for any advice you can send my way -- even if it is bad news (at least I'll know where I stand) Notice: This electronic transmission is intended for the sole use of the individual or entity to which it is addressed and may contain confidential, privileged or otherwise legally protected information. If you are not the intended recipient, or if you believe you are not the intended recipient, you are hereby notified that any use, disclosure, copying, distribution, or the taking of any action in reliance on the contents of this information, is strictly prohibited. Niagara County is not responsible for the content of any external hyperlink referenced in this email or any email. IF YOU HAVE RECEIVED THIS TRANSMISSION IN ERROR, PLEASE NOTIFY THE SENDER IMMEDIATELY BY EMAIL AND DELETE THE ORIGINAL MESSAGE ALONG WITH ANY PAPER OR ELECTRONIC COPIES. Thank you for your cooperation. -- 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 jimdettman at verizon.net Thu Jun 18 13:27:45 2020 From: jimdettman at verizon.net (Jim Dettman) Date: Thu, 18 Jun 2020 14:27:45 -0400 Subject: [AccessD] Word Automation In-Reply-To: References: Message-ID: <020f01d6459e$2999e870$7ccdb950$@verizon.net> I can do that if need be. Jim. -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock via AccessD Sent: Thursday, June 18, 2020 10:36 AM To: Access Developers discussion and problem solving Cc: Gustav Brock Subject: Re: [AccessD] Word Automation Hi John If 20 years old, it probably is of version Access 97. You will need Access 2000/2002/XP/2003 to open this and convert it to Access 2000+. That converted file you can open with Access 2007+ (and convert to the accdb format if you like). /gustav -----Oprindelig meddelelse----- Fra: AccessD P? vegne af John W. Clark Sendt: 18. juni 2020 16:28 Til: Access Developers discussion and problem solving Emne: Re: [AccessD] Word Automation Need help -- not in the Access game too much these days, but some of the old programs still haunt me from time to time. And that is the case now -- a program that was written 20 years ago is rearing it's ugly head. The program has been all but replaced but still holds a use as a "historical" lookup (it is a local resource for quick access to date for them). The recently had new PCs installed and are now on Windows 10 with, I believe Access 2016 (???). In any event I am trying to open this too, and I have 2016. Back when I used Access more, it would come up and ask if you wanted to update an older DB. I was hoping it did this, but it just says it cannot open it. Am I out of luck here? Thanks for any advice you can send my way -- even if it is bad news (at least I'll know where I stand) -- 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 Jun 21 01:29:52 2020 From: newsgrps at dalyn.co.nz (David Emerson) Date: Sun, 21 Jun 2020 18:29:52 +1200 Subject: [AccessD] Rich Text Field Data from Azure Not Showing Message-ID: <00bd01d64795$615d9330$2418b990$@dalyn.co.nz> Hi Listers, Sorry about the cross post but my client has decided to go live tomorrow and there is an annoying problem I would like to solve. They have an existing SQL Server database that has been migrated to Azure. The Access front end is an accdb. There are three tables that have varchar(MAX) datatypes which are used to populate text fields in Access that have their text Format properties set to Rich Text. This works as expected with the text in the fields being able to be formatted. After migrating to Azure and only needing to change the connection strings the Access file works as per the current system with the exception that the Rich Text fields do not display any data! I can enter data in the field and it saves to the table but as soon as I refresh the screen nothing is shown in the field (it is still in the underlying table in SQL though). Normally I get the data for my forms using ADODB.Recordsets. When I put a msgbox line in the VBA to show the contents of the field it comes up with Null. However, when I create a direct link to the table in the Tables Group and open the table I can see the text in the field with all the rich text formatting. Is there something about Azure and ADODB that doesn't like varchar(MAX) data types? Regards David Emerson Dalyn Software Ltd Wellington, New Zealand From paul.hartland at googlemail.com Sun Jun 21 01:42:37 2020 From: paul.hartland at googlemail.com (Paul Hartland) Date: Sun, 21 Jun 2020 07:42:37 +0100 Subject: [AccessD] Rich Text Field Data from Azure Not Showing In-Reply-To: <00bd01d64795$615d9330$2418b990$@dalyn.co.nz> References: <00bd01d64795$615d9330$2418b990$@dalyn.co.nz> Message-ID: I think I remember something about this but only on mobile at moment so cant look up any notes, is it possible to try changing the varchar from varchar(max) to varchar(8000) as a quick test. Paul On Sun, 21 Jun 2020, 07:30 David Emerson, wrote: > Hi Listers, > > > > Sorry about the cross post but my client has decided to go live tomorrow > and > there is an annoying problem I would like to solve. > > > > They have an existing SQL Server database that has been migrated to Azure. > The Access front end is an accdb. There are three tables that have > varchar(MAX) datatypes which are used to populate text fields in Access > that > have their text Format properties set to Rich Text. This works as expected > with the text in the fields being able to be formatted. > > > > After migrating to Azure and only needing to change the connection strings > the Access file works as per the current system with the exception that the > Rich Text fields do not display any data! > > > > I can enter data in the field and it saves to the table but as soon as I > refresh the screen nothing is shown in the field (it is still in the > underlying table in SQL though). > > > > Normally I get the data for my forms using ADODB.Recordsets. When I put a > msgbox line in the VBA to show the contents of the field it comes up with > Null. However, when I create a direct link to the table in the Tables > Group and open the table I can see the text in the field with all the rich > text formatting. > > > > Is there something about Azure and ADODB that doesn't like varchar(MAX) > data > types? > > > > 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 newsgrps at dalyn.co.nz Sun Jun 21 01:54:52 2020 From: newsgrps at dalyn.co.nz (David Emerson) Date: Sun, 21 Jun 2020 18:54:52 +1200 Subject: [AccessD] Rich Text Field Data from Azure Not Showing In-Reply-To: References: <00bd01d64795$615d9330$2418b990$@dalyn.co.nz> Message-ID: <00c801d64798$df78df10$9e6a9d30$@dalyn.co.nz> I am reluctant to do that at this stage because it is their live data that we are working on (the original UAT testing didn't show this as a problem) :( -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Paul Hartland via AccessD Sent: Sunday, 21 June 2020 6:43 p.m. To: Access Developers discussion and problem solving Cc: Paul Hartland Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing I think I remember something about this but only on mobile at moment so cant look up any notes, is it possible to try changing the varchar from varchar(max) to varchar(8000) as a quick test. Paul On Sun, 21 Jun 2020, 07:30 David Emerson, wrote: Sorry about the cross post but my client has decided to go live tomorrow and there is an annoying problem I would like to solve. They have an existing SQL Server database that has been migrated to Azure. The Access front end is an accdb. There are three tables that have varchar(MAX) datatypes which are used to populate text fields in Access that have their text Format properties set to Rich Text. This works as expected with the text in the fields being able to be formatted. After migrating to Azure and only needing to change the connection strings the Access file works as per the current system with the exception that the Rich Text fields do not display any data! I can enter data in the field and it saves to the table but as soon as I refresh the screen nothing is shown in the field (it is still in the underlying table in SQL though). Normally I get the data for my forms using ADODB.Recordsets. When I put a msgbox line in the VBA to show the contents of the field it comes up with Null. However, when I create a direct link to the table in the Tables Group and open the table I can see the text in the field with all the rich text formatting. Is there something about Azure and ADODB that doesn't like varchar(MAX) data types? Regards David Emerson Dalyn Software Ltd Wellington, New Zealand From newsgrps at dalyn.co.nz Sun Jun 21 14:58:48 2020 From: newsgrps at dalyn.co.nz (David Emerson) Date: Mon, 22 Jun 2020 07:58:48 +1200 Subject: [AccessD] Rich Text Field Data from Azure Not Showing In-Reply-To: <00c801d64798$df78df10$9e6a9d30$@dalyn.co.nz> References: <00bd01d64795$615d9330$2418b990$@dalyn.co.nz> <00c801d64798$df78df10$9e6a9d30$@dalyn.co.nz> Message-ID: <003201d64806$630f5080$292df180$@dalyn.co.nz> I was able to make the change to varchar(8000) and that fixed it. Thanks for your help. Regards, David -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson Sent: Sunday, 21 June 2020 6:55 p.m. To: 'Access Developers discussion and problem solving' Cc: 'Paul Hartland' Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing I am reluctant to do that at this stage because it is their live data that we are working on (the original UAT testing didn't show this as a problem) :( -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Paul Hartland via AccessD Sent: Sunday, 21 June 2020 6:43 p.m. To: Access Developers discussion and problem solving Cc: Paul Hartland Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing I think I remember something about this but only on mobile at moment so cant look up any notes, is it possible to try changing the varchar from varchar(max) to varchar(8000) as a quick test. Paul On Sun, 21 Jun 2020, 07:30 David Emerson, wrote: Sorry about the cross post but my client has decided to go live tomorrow and there is an annoying problem I would like to solve. They have an existing SQL Server database that has been migrated to Azure. The Access front end is an accdb. There are three tables that have varchar(MAX) datatypes which are used to populate text fields in Access that have their text Format properties set to Rich Text. This works as expected with the text in the fields being able to be formatted. After migrating to Azure and only needing to change the connection strings the Access file works as per the current system with the exception that the Rich Text fields do not display any data! I can enter data in the field and it saves to the table but as soon as I refresh the screen nothing is shown in the field (it is still in the underlying table in SQL though). Normally I get the data for my forms using ADODB.Recordsets. When I put a msgbox line in the VBA to show the contents of the field it comes up with Null. However, when I create a direct link to the table in the Tables Group and open the table I can see the text in the field with all the rich text formatting. Is there something about Azure and ADODB that doesn't like varchar(MAX) data types? Regards David Emerson Dalyn Software Ltd Wellington, New Zealand From newsgrps at dalyn.co.nz Mon Jun 22 23:13:27 2020 From: newsgrps at dalyn.co.nz (David Emerson) Date: Tue, 23 Jun 2020 16:13:27 +1200 Subject: [AccessD] Access 365 and Azure - DateTime fields Message-ID: <00bb01d64914$a76ab490$f6401db0$@dalyn.co.nz> 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-client-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 Jun 23 00:57:10 2020 From: newsgrps at dalyn.co.nz (David Emerson) Date: Tue, 23 Jun 2020 17:57:10 +1200 Subject: [AccessD] Access 365 and Azure - DateTime fields In-Reply-To: <00bb01d64914$a76ab490$f6401db0$@dalyn.co.nz> References: <00bb01d64914$a76ab490$f6401db0$@dalyn.co.nz> Message-ID: <010a01d64923$245e6f60$6d1b4e20$@dalyn.co.nz> Further information - I notice that some records can be changed and some can't. The difference seems to be in the decimals stored in the field. For example, a record with the first date in a field will not save, but zeroing the decimals will enable it to be saved (see second date): 2020-06-23 17:21:32.312 2020-06-23 17:21:32.000 This is true whether the field changed is a date field or any other field type. It seems that the presence of just one field with non-zero decimal places in a date field will cause the problem. It looks like I need to clear out the fractions of seconds from my datetime fields. Does anyone have a simple SQL Query I could use to do this? David -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson Sent: Tuesday, 23 June 2020 4:13 p.m. To: AccessD Subject: [AccessD] Access 365 and Azure - DateTime fields 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-client-100- datetime.html Can anyone steer me in the right direction? Regards David Emerson Dalyn Software Ltd Wellington, New Zealand From paul.hartland at googlemail.com Tue Jun 23 01:25:45 2020 From: paul.hartland at googlemail.com (Paul Hartland) Date: Tue, 23 Jun 2020 07:25:45 +0100 Subject: [AccessD] Access 365 and Azure - DateTime fields In-Reply-To: <010a01d64923$245e6f60$6d1b4e20$@dalyn.co.nz> References: <00bb01d64914$a76ab490$f6401db0$@dalyn.co.nz> <010a01d64923$245e6f60$6d1b4e20$@dalyn.co.nz> Message-ID: To clear the millisecond just take it away from the date i.e. update yourtable Set yourdatefield = dateadd(millisecond, -(datepart(millisecond, yourdatefield)), yourdatefield) Paul On Tue, 23 Jun 2020, 06:57 David Emerson, wrote: > Further information - I notice that some records can be changed and some > can't. The difference seems to be in the decimals stored in the field. > For > example, a record with the first date in a field will not save, but zeroing > the decimals will enable it to be saved (see second date): > 2020-06-23 17:21:32.312 > 2020-06-23 17:21:32.000 > > This is true whether the field changed is a date field or any other field > type. It seems that the presence of just one field with non-zero decimal > places in a date field will cause the problem. > > It looks like I need to clear out the fractions of seconds from my datetime > fields. Does anyone have a simple SQL Query I could use to do this? > > David > > -----Original Message----- > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of > David Emerson > Sent: Tuesday, 23 June 2020 4:13 p.m. > To: AccessD > Subject: [AccessD] Access 365 and Azure - DateTime fields > > 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-client-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 > From stuart at lexacorp.com.pg Tue Jun 23 02:30:13 2020 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Tue, 23 Jun 2020 17:30:13 +1000 Subject: [AccessD] Access 365 and Azure - DateTime fields In-Reply-To: <00bb01d64914$a76ab490$f6401db0$@dalyn.co.nz> References: <00bb01d64914$a76ab490$f6401db0$@dalyn.co.nz> Message-ID: <5EF1AF85.16578.4AD63AA@stuart.lexacorp.com.pg> Try changing the field to datetime2. https://docs.microsoft.com/en-us/sql/t-sql/data-types/datetime-transact-sql?view=sql-server-v er15 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. 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-clien > 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 > From stuart at lexacorp.com.pg Tue Jun 23 02:34:24 2020 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Tue, 23 Jun 2020 17:34:24 +1000 Subject: [AccessD] Access 365 and Azure - DateTime fields In-Reply-To: <5EF1AF85.16578.4AD63AA@stuart.lexacorp.com.pg> References: <00bb01d64914$a76ab490$f6401db0$@dalyn.co.nz>, <5EF1AF85.16578.4AD63AA@stuart.lexacorp.com.pg> Message-ID: <5EF1B080.7052.4B13A98@stuart.lexacorp.com.pg> 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 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. > > 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 > From newsgrps at dalyn.co.nz Tue Jun 23 02:52:00 2020 From: newsgrps at dalyn.co.nz (David Emerson) Date: Tue, 23 Jun 2020 19:52:00 +1200 Subject: [AccessD] Access 365 and Azure - DateTime fields In-Reply-To: <5EF1B080.7052.4B13A98@stuart.lexacorp.com.pg> References: <00bb01d64914$a76ab490$f6401db0$@dalyn.co.nz>, <5EF1AF85.16578.4AD63AA@stuart.lexacorp.com.pg> <5EF1B080.7052.4B13A98@stuart.lexacorp.com.pg> Message-ID: <010e01d64933$2f5b9860$8e12c920$@dalyn.co.nz> 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 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. > > 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 Wed Jun 24 22:49:50 2020 From: newsgrps at dalyn.co.nz (David Emerson) Date: Thu, 25 Jun 2020 15:49:50 +1200 Subject: [AccessD] Rich Text Field Data from Azure Not Showing In-Reply-To: <003201d64806$630f5080$292df180$@dalyn.co.nz> References: <00bd01d64795$615d9330$2418b990$@dalyn.co.nz> <00c801d64798$df78df10$9e6a9d30$@dalyn.co.nz> <003201d64806$630f5080$292df180$@dalyn.co.nz> Message-ID: <002001d64aa3$afe03740$0fa0a5c0$@dalyn.co.nz> Further to below, we can see the data in the fields in Access now but we have the problem that we are limited to about 3000 characters depending on the formatting (bold, italics, etc) which takes up extra storage. The client uses this field for pasting email body information which often goes over this limitation. Does anyone have a solution to this dilemma? Regards, David -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson Sent: Monday, 22 June 2020 7:59 a.m. To: 'Access Developers discussion and problem solving' Cc: 'Paul Hartland' Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing I was able to make the change to varchar(8000) and that fixed it. Thanks for your help. Regards, David -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson Sent: Sunday, 21 June 2020 6:55 p.m. To: 'Access Developers discussion and problem solving' Cc: 'Paul Hartland' Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing I am reluctant to do that at this stage because it is their live data that we are working on (the original UAT testing didn't show this as a problem) :( -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Paul Hartland via AccessD Sent: Sunday, 21 June 2020 6:43 p.m. To: Access Developers discussion and problem solving Cc: Paul Hartland Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing I think I remember something about this but only on mobile at moment so cant look up any notes, is it possible to try changing the varchar from varchar(max) to varchar(8000) as a quick test. Paul On Sun, 21 Jun 2020, 07:30 David Emerson, wrote: Sorry about the cross post but my client has decided to go live tomorrow and there is an annoying problem I would like to solve. They have an existing SQL Server database that has been migrated to Azure. The Access front end is an accdb. There are three tables that have varchar(MAX) datatypes which are used to populate text fields in Access that have their text Format properties set to Rich Text. This works as expected with the text in the fields being able to be formatted. After migrating to Azure and only needing to change the connection strings the Access file works as per the current system with the exception that the Rich Text fields do not display any data! I can enter data in the field and it saves to the table but as soon as I refresh the screen nothing is shown in the field (it is still in the underlying table in SQL though). Normally I get the data for my forms using ADODB.Recordsets. When I put a msgbox line in the VBA to show the contents of the field it comes up with Null. However, when I create a direct link to the table in the Tables Group and open the table I can see the text in the field with all the rich text formatting. Is there something about Azure and ADODB that doesn't like varchar(MAX) data types? 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 newsgrps at dalyn.co.nz Thu Jun 25 00:10:54 2020 From: newsgrps at dalyn.co.nz (David Emerson) Date: Thu, 25 Jun 2020 17:10:54 +1200 Subject: [AccessD] Rich Text Field Data from Azure Not Showing In-Reply-To: References: <00bd01d64795$615d9330$2418b990$@dalyn.co.nz> <00c801d64798$df78df10$9e6a9d30$@dalyn.co.nz> <003201d64806$630f5080$292df180$@dalyn.co.nz> <002001d64aa3$afe03740$0fa0a5c0$@dalyn.co.nz> Message-ID: <003601d64aaf$029c53a0$07d4fae0$@dalyn.co.nz> Hi Paul, The limit is an estimation of the visible characters. Because it is Rich Text there are all also the formatting characters that are not seen in the screen field but are stored in the table field. The total number of characters I am guessing is 8000. Whatever it is, it is not enough. Changing it to varchar(MAX) allowed more characters to be stored but they weren?t being displayed in the Access screen textbox. What would be nice would be to have the field as varchar(MAX) and also showing in the Access form J Regards, David From: Paul Hartland [mailto:paul.hartland at googlemail.com] Sent: Thursday, 25 June 2020 5:00 p.m. To: David Emerson Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing Not long woke up, checked email and saw this this sounds very similar to a problem we had at an old company, when you say you are limited to about 3000 characters, do you mean in the rich text box field itself or the physical field of the table ? I think our problem was we had the data in the fields but unable to display it all in the rich text box. Paul On Thu, 25 Jun 2020, 04:50 David Emerson, wrote: Further to below, we can see the data in the fields in Access now but we have the problem that we are limited to about 3000 characters depending on the formatting (bold, italics, etc) which takes up extra storage. The client uses this field for pasting email body information which often goes over this limitation. Does anyone have a solution to this dilemma? Regards, David -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson Sent: Monday, 22 June 2020 7:59 a.m. To: 'Access Developers discussion and problem solving' Cc: 'Paul Hartland' Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing I was able to make the change to varchar(8000) and that fixed it. Thanks for your help. Regards, David -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson Sent: Sunday, 21 June 2020 6:55 p.m. To: 'Access Developers discussion and problem solving' Cc: 'Paul Hartland' Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing I am reluctant to do that at this stage because it is their live data that we are working on (the original UAT testing didn't show this as a problem) :( -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Paul Hartland via AccessD Sent: Sunday, 21 June 2020 6:43 p.m. To: Access Developers discussion and problem solving Cc: Paul Hartland Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing I think I remember something about this but only on mobile at moment so cant look up any notes, is it possible to try changing the varchar from varchar(max) to varchar(8000) as a quick test. Paul On Sun, 21 Jun 2020, 07:30 David Emerson, wrote: Sorry about the cross post but my client has decided to go live tomorrow and there is an annoying problem I would like to solve. They have an existing SQL Server database that has been migrated to Azure. The Access front end is an accdb. There are three tables that have varchar(MAX) datatypes which are used to populate text fields in Access that have their text Format properties set to Rich Text. This works as expected with the text in the fields being able to be formatted. After migrating to Azure and only needing to change the connection strings the Access file works as per the current system with the exception that the Rich Text fields do not display any data! I can enter data in the field and it saves to the table but as soon as I refresh the screen nothing is shown in the field (it is still in the underlying table in SQL though). Normally I get the data for my forms using ADODB.Recordsets. When I put a msgbox line in the VBA to show the contents of the field it comes up with Null. However, when I create a direct link to the table in the Tables Group and open the table I can see the text in the field with all the rich text formatting. Is there something about Azure and ADODB that doesn't like varchar(MAX) data types? Regards David Emerson Dalyn Software Ltd Wellington, New Zealand From jimdettman at verizon.net Thu Jun 25 07:16:27 2020 From: jimdettman at verizon.net (Jim Dettman) Date: Thu, 25 Jun 2020 08:16:27 -0400 Subject: [AccessD] Rich Text Field Data from Azure Not Showing In-Reply-To: <002001d64aa3$afe03740$0fa0a5c0$@dalyn.co.nz> References: <00bd01d64795$615d9330$2418b990$@dalyn.co.nz> <00c801d64798$df78df10$9e6a9d30$@dalyn.co.nz> <003201d64806$630f5080$292df180$@dalyn.co.nz> <002001d64aa3$afe03740$0fa0a5c0$@dalyn.co.nz> Message-ID: <00ca01d64aea$741b30b0$5c519210$@verizon.net> I would think the problem relates to the SQL driver you are using and would want to use the SQL Native driver. That's the only way you are going to pick up the newer features in SQL/Azure. I'm still mostly stuck in the stone ages (pre SQL 2005), so it's not something I've played with, but from reading other questions/problems, that's probably where the problem lies. A lot changed in SQL with 2005 and specifically with this, the way BLOB fields were terminated. Jim. -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson Sent: Wednesday, June 24, 2020 11:50 PM To: 'Access Developers discussion and problem solving' Cc: 'Paul Hartland' Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing Further to below, we can see the data in the fields in Access now but we have the problem that we are limited to about 3000 characters depending on the formatting (bold, italics, etc) which takes up extra storage. The client uses this field for pasting email body information which often goes over this limitation. Does anyone have a solution to this dilemma? Regards, David -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson Sent: Monday, 22 June 2020 7:59 a.m. To: 'Access Developers discussion and problem solving' Cc: 'Paul Hartland' Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing I was able to make the change to varchar(8000) and that fixed it. Thanks for your help. Regards, David -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson Sent: Sunday, 21 June 2020 6:55 p.m. To: 'Access Developers discussion and problem solving' Cc: 'Paul Hartland' Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing I am reluctant to do that at this stage because it is their live data that we are working on (the original UAT testing didn't show this as a problem) :( -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Paul Hartland via AccessD Sent: Sunday, 21 June 2020 6:43 p.m. To: Access Developers discussion and problem solving Cc: Paul Hartland Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing I think I remember something about this but only on mobile at moment so cant look up any notes, is it possible to try changing the varchar from varchar(max) to varchar(8000) as a quick test. Paul On Sun, 21 Jun 2020, 07:30 David Emerson, wrote: Sorry about the cross post but my client has decided to go live tomorrow and there is an annoying problem I would like to solve. They have an existing SQL Server database that has been migrated to Azure. The Access front end is an accdb. There are three tables that have varchar(MAX) datatypes which are used to populate text fields in Access that have their text Format properties set to Rich Text. This works as expected with the text in the fields being able to be formatted. After migrating to Azure and only needing to change the connection strings the Access file works as per the current system with the exception that the Rich Text fields do not display any data! I can enter data in the field and it saves to the table but as soon as I refresh the screen nothing is shown in the field (it is still in the underlying table in SQL though). Normally I get the data for my forms using ADODB.Recordsets. When I put a msgbox line in the VBA to show the contents of the field it comes up with Null. However, when I create a direct link to the table in the Tables Group and open the table I can see the text in the field with all the rich text formatting. Is there something about Azure and ADODB that doesn't like varchar(MAX) data types? 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 From newsgrps at dalyn.co.nz Thu Jun 25 15:14:27 2020 From: newsgrps at dalyn.co.nz (David Emerson) Date: Fri, 26 Jun 2020 08:14:27 +1200 Subject: [AccessD] Rich Text Field Data from Azure Not Showing In-Reply-To: <00ca01d64aea$741b30b0$5c519210$@verizon.net> References: <00bd01d64795$615d9330$2418b990$@dalyn.co.nz> <00c801d64798$df78df10$9e6a9d30$@dalyn.co.nz> <003201d64806$630f5080$292df180$@dalyn.co.nz> <002001d64aa3$afe03740$0fa0a5c0$@dalyn.co.nz> <00ca01d64aea$741b30b0$5c519210$@verizon.net> Message-ID: <001501d64b2d$3c2ad5a0$b48080e0$@dalyn.co.nz> This is the driver we are using for the connection string: gADODBConnection.ConnectionString = "Driver={ODBC Driver 17 for SQL Server};Server=tcp:prism-prd-failover.database.windows.net,1433;Database=Pri sm-prd-db;UID=USER;Pwd=VERYSECUREPWD;Encrypt=yes;TrustServerCertificate=no;C onnection Timeout=60" David -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman via AccessD Sent: Friday, 26 June 2020 12:16 a.m. To: 'Access Developers discussion and problem solving' Cc: Jim Dettman; 'Paul Hartland' Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing I would think the problem relates to the SQL driver you are using and would want to use the SQL Native driver. That's the only way you are going to pick up the newer features in SQL/Azure. I'm still mostly stuck in the stone ages (pre SQL 2005), so it's not something I've played with, but from reading other questions/problems, that's probably where the problem lies. A lot changed in SQL with 2005 and specifically with this, the way BLOB fields were terminated. Jim. -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson Sent: Wednesday, June 24, 2020 11:50 PM To: 'Access Developers discussion and problem solving' Cc: 'Paul Hartland' Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing Further to below, we can see the data in the fields in Access now but we have the problem that we are limited to about 3000 characters depending on the formatting (bold, italics, etc) which takes up extra storage. The client uses this field for pasting email body information which often goes over this limitation. Does anyone have a solution to this dilemma? Regards, David -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson Sent: Monday, 22 June 2020 7:59 a.m. To: 'Access Developers discussion and problem solving' Cc: 'Paul Hartland' Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing I was able to make the change to varchar(8000) and that fixed it. Thanks for your help. Regards, David -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of David Emerson Sent: Sunday, 21 June 2020 6:55 p.m. To: 'Access Developers discussion and problem solving' Cc: 'Paul Hartland' Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing I am reluctant to do that at this stage because it is their live data that we are working on (the original UAT testing didn't show this as a problem) :( -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Paul Hartland via AccessD Sent: Sunday, 21 June 2020 6:43 p.m. To: Access Developers discussion and problem solving Cc: Paul Hartland Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing I think I remember something about this but only on mobile at moment so cant look up any notes, is it possible to try changing the varchar from varchar(max) to varchar(8000) as a quick test. Paul On Sun, 21 Jun 2020, 07:30 David Emerson, wrote: Sorry about the cross post but my client has decided to go live tomorrow and there is an annoying problem I would like to solve. They have an existing SQL Server database that has been migrated to Azure. The Access front end is an accdb. There are three tables that have varchar(MAX) datatypes which are used to populate text fields in Access that have their text Format properties set to Rich Text. This works as expected with the text in the fields being able to be formatted. After migrating to Azure and only needing to change the connection strings the Access file works as per the current system with the exception that the Rich Text fields do not display any data! I can enter data in the field and it saves to the table but as soon as I refresh the screen nothing is shown in the field (it is still in the underlying table in SQL though). Normally I get the data for my forms using ADODB.Recordsets. When I put a msgbox line in the VBA to show the contents of the field it comes up with Null. However, when I create a direct link to the table in the Tables Group and open the table I can see the text in the field with all the rich text formatting. Is there something about Azure and ADODB that doesn't like varchar(MAX) data types? 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 Thu Jun 25 15:25:57 2020 From: newsgrps at dalyn.co.nz (David Emerson) Date: Fri, 26 Jun 2020 08:25:57 +1200 Subject: [AccessD] Access 365 and Azure - DateTime fields In-Reply-To: <010e01d64933$2f5b9860$8e12c920$@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> Message-ID: <001601d64b2e$d740df20$85c29d60$@dalyn.co.nz> 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 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. > > 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 stuart at lexacorp.com.pg Thu Jun 25 17:38:30 2020 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Fri, 26 Jun 2020 08:38:30 +1000 Subject: [AccessD] Rich Text Field Data from Azure Not Showing In-Reply-To: <001501d64b2d$3c2ad5a0$b48080e0$@dalyn.co.nz> References: <00bd01d64795$615d9330$2418b990$@dalyn.co.nz>, <00ca01d64aea$741b30b0$5c519210$@verizon.net>, <001501d64b2d$3c2ad5a0$b48080e0$@dalyn.co.nz> Message-ID: <5EF52766.6103.1239AC83@stuart.lexacorp.com.pg> Try the OLEDB driver rather than ODBC https://docs.microsoft.com/en-us/sql/connect/oledb/oledb-driver-for-sql-server?view=sql-serv er-ver15 "OLE DB was undeprecated and released in 2018. The new OLE DB provider is called the Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL). The new provider will be updated with the most recent server features going forward." On 26 Jun 2020 at 8:14, David Emerson wrote: > This is the driver we are using for the connection string: > > gADODBConnection.ConnectionString = "Driver={ODBC Driver 17 for SQL > Server};Server=tcp:prism-prd-failover.database.windows.net,1433;Databa > se=Pri > sm-prd-db;UID=USER;Pwd=VERYSECUREPWD;Encrypt=yes;TrustServerCertificat > e=no;C onnection Timeout=60" > > David > > -----Original Message----- > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf > Of Jim Dettman via AccessD Sent: Friday, 26 June 2020 12:16 a.m. To: > 'Access Developers discussion and problem solving' Cc: Jim Dettman; > 'Paul Hartland' Subject: Re: [AccessD] Rich Text Field Data from Azure > Not Showing > > > I would think the problem relates to the SQL driver you are using and > would > want to use the SQL Native driver. > > That's the only way you are going to pick up the newer features in > SQL/Azure. > > I'm still mostly stuck in the stone ages (pre SQL 2005), so it's not > something I've played with, but from reading other questions/problems, > that's probably where the problem lies. A lot changed in SQL with > 2005 and specifically with this, the way BLOB fields were terminated. > > Jim. > > -----Original Message----- > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf > Of David Emerson Sent: Wednesday, June 24, 2020 11:50 PM To: 'Access > Developers discussion and problem solving' Cc: 'Paul Hartland' > Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing > > Further to below, we can see the data in the fields in Access now but > we have the problem that we are limited to about 3000 characters > depending on the formatting (bold, italics, etc) which takes up extra > storage. The client uses this field for pasting email body > information which often goes over this limitation. > > Does anyone have a solution to this dilemma? > > Regards, David > > -----Original Message----- > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf > Of David Emerson Sent: Monday, 22 June 2020 7:59 a.m. To: 'Access > Developers discussion and problem solving' Cc: 'Paul Hartland' > Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing > > I was able to make the change to varchar(8000) and that fixed it. > Thanks for your help. > > Regards, David > > -----Original Message----- > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf > Of David Emerson Sent: Sunday, 21 June 2020 6:55 p.m. To: 'Access > Developers discussion and problem solving' Cc: 'Paul Hartland' > Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing > > I am reluctant to do that at this stage because it is their live data > that we are working on (the original UAT testing didn't show this as a > problem) :( > > -----Original Message----- > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf > Of Paul Hartland via AccessD Sent: Sunday, 21 June 2020 6:43 p.m. To: > Access Developers discussion and problem solving Cc: Paul Hartland > Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing > > I think I remember something about this but only on mobile at moment > so cant look up any notes, is it possible to try changing the varchar > from varchar(max) to varchar(8000) as a quick test. > > Paul > > > On Sun, 21 Jun 2020, 07:30 David Emerson, > wrote: > > Sorry about the cross post but my client has decided to go live > tomorrow and there is an annoying problem I would like to solve. > > They have an existing SQL Server database that has been migrated to > Azure. The Access front end is an accdb. There are three tables that > have varchar(MAX) datatypes which are used to populate text fields in > Access that have their text Format properties set to Rich Text. This > works as expected with the text in the fields being able to be > formatted. > > After migrating to Azure and only needing to change the connection > strings the Access file works as per the current system with the > exception that the Rich Text fields do not display any data! > > I can enter data in the field and it saves to the table but as soon as > I refresh the screen nothing is shown in the field (it is still in the > underlying table in SQL though). > > Normally I get the data for my forms using ADODB.Recordsets. When I > put a msgbox line in the VBA to show the contents of the field it > comes up with Null. However, when I create a direct link to the > table in the Tables Group and open the table I can see the text in the > field with all the rich text formatting. > > Is there something about Azure and ADODB that doesn't like > varchar(MAX) data types? > > 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 > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > From bensonforums at gmail.com Thu Jun 25 21:25:05 2020 From: bensonforums at gmail.com (Bill Benson) Date: Thu, 25 Jun 2020 22:25:05 -0400 Subject: [AccessD] Access 365 and Azure - DateTime fields In-Reply-To: <001601d64b2e$d740df20$85c29d60$@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> Message-ID: Is there a possibility of the system clock flipping to a new value exactly in between the point when it calculates one of the two GETDATE() functions, and the other? On Thu, Jun 25, 2020 at 4:26 PM David Emerson 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 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. > > > > 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 > From stuart at lexacorp.com.pg Thu Jun 25 22:23:54 2020 From: stuart at lexacorp.com.pg (Stuart McLachlan) Date: Fri, 26 Jun 2020 13:23:54 +1000 Subject: [AccessD] Access 365 and Azure - DateTime fields In-Reply-To: References: <00bb01d64914$a76ab490$f6401db0$@dalyn.co.nz>, <001601d64b2e$d740df20$85c29d60$@dalyn.co.nz>, Message-ID: <5EF56A4A.3963.133EF7AB@stuart.lexacorp.com.pg> Sure is. :( On 25 Jun 2020 at 22:25, Bill Benson wrote: > Is there a possibility of the system clock flipping to a new value > exactly in between the point when it calculates one of the two > GETDATE() functions, and the other? > > On Thu, Jun 25, 2020 at 4:26 PM David Emerson > 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-tra > > > nsac t-sql?view=sql-server-v er15 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. > > > > > > > > > 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 > From paul.hartland at googlemail.com Thu Jun 25 23:45:32 2020 From: paul.hartland at googlemail.com (Paul Hartland) Date: Fri, 26 Jun 2020 05:45:32 +0100 Subject: [AccessD] Access 365 and Azure - DateTime fields In-Reply-To: <001601d64b2e$d740df20$85c29d60$@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> Message-ID: 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, 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 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. > > > > 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 > From jimdettman at verizon.net Fri Jun 26 08:18:04 2020 From: jimdettman at verizon.net (Jim Dettman) Date: Fri, 26 Jun 2020 09:18:04 -0400 Subject: [AccessD] Rich Text Field Data from Azure Not Showing In-Reply-To: <5EF52766.6103.1239AC83@stuart.lexacorp.com.pg> References: <00bd01d64795$615d9330$2418b990$@dalyn.co.nz>, <00ca01d64aea$741b30b0$5c519210$@verizon.net>, <001501d64b2d$3c2ad5a0$b48080e0$@dalyn.co.nz> <5EF52766.6103.1239AC83@stuart.lexacorp.com.pg> Message-ID: <020001d64bbc$3a16dcc0$ae449640$@verizon.net> Did a little digging on the drivers and there is a good article here covering what's available and what's not: https://accessexperts.com/blog/2018/09/11/new-sql-server-odbc-and-oledb-driv er/ Jim. -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Thursday, June 25, 2020 6:38 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing Try the OLEDB driver rather than ODBC https://docs.microsoft.com/en-us/sql/connect/oledb/oledb-driver-for-sql-serv er?view=sql-serv er-ver15 "OLE DB was undeprecated and released in 2018. The new OLE DB provider is called the Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL). The new provider will be updated with the most recent server features going forward." On 26 Jun 2020 at 8:14, David Emerson wrote: > This is the driver we are using for the connection string: > > gADODBConnection.ConnectionString = "Driver={ODBC Driver 17 for SQL > Server};Server=tcp:prism-prd-failover.database.windows.net,1433;Databa > se=Pri > sm-prd-db;UID=USER;Pwd=VERYSECUREPWD;Encrypt=yes;TrustServerCertificat > e=no;C onnection Timeout=60" > > David > > -----Original Message----- > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf > Of Jim Dettman via AccessD Sent: Friday, 26 June 2020 12:16 a.m. To: > 'Access Developers discussion and problem solving' Cc: Jim Dettman; > 'Paul Hartland' Subject: Re: [AccessD] Rich Text Field Data from Azure > Not Showing > > > I would think the problem relates to the SQL driver you are using and > would > want to use the SQL Native driver. > > That's the only way you are going to pick up the newer features in > SQL/Azure. > > I'm still mostly stuck in the stone ages (pre SQL 2005), so it's not > something I've played with, but from reading other questions/problems, > that's probably where the problem lies. A lot changed in SQL with > 2005 and specifically with this, the way BLOB fields were terminated. > > Jim. > > -----Original Message----- > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf > Of David Emerson Sent: Wednesday, June 24, 2020 11:50 PM To: 'Access > Developers discussion and problem solving' Cc: 'Paul Hartland' > Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing > > Further to below, we can see the data in the fields in Access now but > we have the problem that we are limited to about 3000 characters > depending on the formatting (bold, italics, etc) which takes up extra > storage. The client uses this field for pasting email body > information which often goes over this limitation. > > Does anyone have a solution to this dilemma? > > Regards, David > > -----Original Message----- > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf > Of David Emerson Sent: Monday, 22 June 2020 7:59 a.m. To: 'Access > Developers discussion and problem solving' Cc: 'Paul Hartland' > Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing > > I was able to make the change to varchar(8000) and that fixed it. > Thanks for your help. > > Regards, David > > -----Original Message----- > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf > Of David Emerson Sent: Sunday, 21 June 2020 6:55 p.m. To: 'Access > Developers discussion and problem solving' Cc: 'Paul Hartland' > Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing > > I am reluctant to do that at this stage because it is their live data > that we are working on (the original UAT testing didn't show this as a > problem) :( > > -----Original Message----- > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf > Of Paul Hartland via AccessD Sent: Sunday, 21 June 2020 6:43 p.m. To: > Access Developers discussion and problem solving Cc: Paul Hartland > Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing > > I think I remember something about this but only on mobile at moment > so cant look up any notes, is it possible to try changing the varchar > from varchar(max) to varchar(8000) as a quick test. > > Paul > > > On Sun, 21 Jun 2020, 07:30 David Emerson, > wrote: > > Sorry about the cross post but my client has decided to go live > tomorrow and there is an annoying problem I would like to solve. > > They have an existing SQL Server database that has been migrated to > Azure. The Access front end is an accdb. There are three tables that > have varchar(MAX) datatypes which are used to populate text fields in > Access that have their text Format properties set to Rich Text. This > works as expected with the text in the fields being able to be > formatted. > > After migrating to Azure and only needing to change the connection > strings the Access file works as per the current system with the > exception that the Rich Text fields do not display any data! > > I can enter data in the field and it saves to the table but as soon as > I refresh the screen nothing is shown in the field (it is still in the > underlying table in SQL though). > > Normally I get the data for my forms using ADODB.Recordsets. When I > put a msgbox line in the VBA to show the contents of the field it > comes up with Null. However, when I create a direct link to the > table in the Tables Group and open the table I can see the text in the > field with all the rich text formatting. > > Is there something about Azure and ADODB that doesn't like > varchar(MAX) data types? > > 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 > > -- > 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 Fri Jun 26 16:19:09 2020 From: newsgrps at dalyn.co.nz (David Emerson) Date: Sat, 27 Jun 2020 09:19:09 +1200 Subject: [AccessD] Access 365 and Azure - DateTime fields In-Reply-To: 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> Message-ID: <002b01d64bff$70b4f760$521ee620$@dalyn.co.nz> 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, 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 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. > > > > 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 From newsgrps at dalyn.co.nz Fri Jun 26 16:20:57 2020 From: newsgrps at dalyn.co.nz (David Emerson) Date: Sat, 27 Jun 2020 09:20:57 +1200 Subject: [AccessD] Rich Text Field Data from Azure Not Showing In-Reply-To: <020001d64bbc$3a16dcc0$ae449640$@verizon.net> References: <00bd01d64795$615d9330$2418b990$@dalyn.co.nz>, <00ca01d64aea$741b30b0$5c519210$@verizon.net>, <001501d64b2d$3c2ad5a0$b48080e0$@dalyn.co.nz> <5EF52766.6103.1239AC83@stuart.lexacorp.com.pg> <020001d64bbc$3a16dcc0$ae449640$@verizon.net> Message-ID: <002c01d64bff$b12453e0$136cfba0$@dalyn.co.nz> Thanks Jim -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman via AccessD Sent: Saturday, 27 June 2020 1:18 a.m. To: 'Access Developers discussion and problem solving' Cc: Jim Dettman Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing Did a little digging on the drivers and there is a good article here covering what's available and what's not: https://accessexperts.com/blog/2018/09/11/new-sql-server-odbc-and-oledb-driv er/ Jim. -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan Sent: Thursday, June 25, 2020 6:38 PM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing Try the OLEDB driver rather than ODBC https://docs.microsoft.com/en-us/sql/connect/oledb/oledb-driver-for-sql-serv er?view=sql-serv er-ver15 "OLE DB was undeprecated and released in 2018. The new OLE DB provider is called the Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL). The new provider will be updated with the most recent server features going forward." On 26 Jun 2020 at 8:14, David Emerson wrote: > This is the driver we are using for the connection string: > > gADODBConnection.ConnectionString = "Driver={ODBC Driver 17 for SQL > Server};Server=tcp:prism-prd-failover.database.windows.net,1433;Databa > se=Pri > sm-prd-db;UID=USER;Pwd=VERYSECUREPWD;Encrypt=yes;TrustServerCertificat > e=no;C onnection Timeout=60" > > David > > -----Original Message----- > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf > Of Jim Dettman via AccessD Sent: Friday, 26 June 2020 12:16 a.m. To: > 'Access Developers discussion and problem solving' Cc: Jim Dettman; > 'Paul Hartland' Subject: Re: [AccessD] Rich Text Field Data from Azure > Not Showing > > > I would think the problem relates to the SQL driver you are using and > would > want to use the SQL Native driver. > > That's the only way you are going to pick up the newer features in > SQL/Azure. > > I'm still mostly stuck in the stone ages (pre SQL 2005), so it's not > something I've played with, but from reading other questions/problems, > that's probably where the problem lies. A lot changed in SQL with > 2005 and specifically with this, the way BLOB fields were terminated. > > Jim. > > -----Original Message----- > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf > Of David Emerson Sent: Wednesday, June 24, 2020 11:50 PM To: 'Access > Developers discussion and problem solving' Cc: 'Paul Hartland' > Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing > > Further to below, we can see the data in the fields in Access now but > we have the problem that we are limited to about 3000 characters > depending on the formatting (bold, italics, etc) which takes up extra > storage. The client uses this field for pasting email body > information which often goes over this limitation. > > Does anyone have a solution to this dilemma? > > Regards, David > > -----Original Message----- > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf > Of David Emerson Sent: Monday, 22 June 2020 7:59 a.m. To: 'Access > Developers discussion and problem solving' Cc: 'Paul Hartland' > Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing > > I was able to make the change to varchar(8000) and that fixed it. > Thanks for your help. > > Regards, David > > -----Original Message----- > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf > Of David Emerson Sent: Sunday, 21 June 2020 6:55 p.m. To: 'Access > Developers discussion and problem solving' Cc: 'Paul Hartland' > Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing > > I am reluctant to do that at this stage because it is their live data > that we are working on (the original UAT testing didn't show this as a > problem) :( > > -----Original Message----- > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf > Of Paul Hartland via AccessD Sent: Sunday, 21 June 2020 6:43 p.m. To: > Access Developers discussion and problem solving Cc: Paul Hartland > Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing > > I think I remember something about this but only on mobile at moment > so cant look up any notes, is it possible to try changing the varchar > from varchar(max) to varchar(8000) as a quick test. > > Paul > > > On Sun, 21 Jun 2020, 07:30 David Emerson, > wrote: > > Sorry about the cross post but my client has decided to go live > tomorrow and there is an annoying problem I would like to solve. > > They have an existing SQL Server database that has been migrated to > Azure. The Access front end is an accdb. There are three tables that > have varchar(MAX) datatypes which are used to populate text fields in > Access that have their text Format properties set to Rich Text. This > works as expected with the text in the fields being able to be > formatted. > > After migrating to Azure and only needing to change the connection > strings the Access file works as per the current system with the > exception that the Rich Text fields do not display any data! > > I can enter data in the field and it saves to the table but as soon as > I refresh the screen nothing is shown in the field (it is still in the > underlying table in SQL though). > > Normally I get the data for my forms using ADODB.Recordsets. When I > put a msgbox line in the VBA to show the contents of the field it > comes up with Null. However, when I create a direct link to the > table in the Tables Group and open the table I can see the text in the > field with all the rich text formatting. > > Is there something about Azure and ADODB that doesn't like > varchar(MAX) data types? > > 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 > > -- > 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 Mon Jun 29 04:44:25 2020 From: newsgrps at dalyn.co.nz (David Emerson) Date: Mon, 29 Jun 2020 21:44:25 +1200 Subject: [AccessD] Rich Text Field Data from Azure Not Showing In-Reply-To: References: <00bd01d64795$615d9330$2418b990$@dalyn.co.nz> <00c801d64798$df78df10$9e6a9d30$@dalyn.co.nz> <003201d64806$630f5080$292df180$@dalyn.co.nz> <002001d64aa3$afe03740$0fa0a5c0$@dalyn.co.nz> <003601d64aaf$029c53a0$07d4fae0$@dalyn.co.nz> <004701d64aba$099bdb70$1cd39250$@dalyn.co.nz> <004f01d64aca$7dfa6760$79ef3620$@dalyn.co.nz> <005c01d64ad4$b0b62ea0$12228be0$@dalyn.co.nz> <006401d64ae2$59d25830$0d770890$@dalyn.co.nz> <001701d64b2f$648a7530$2d9f5f90$@dalyn.co.nz> Message-ID: <011601d64df9$e1ec8d20$a5c5a760$@dalyn.co.nz> Thanks to the help of this group (especially Paul, Stuart and Jim) we solved the problem. The solution was to upgrade to version 18 of the OLE DB Driver and use ?Provider=MSOLEDBSQL? in the connection string. Regards, David From: Paul Hartland [mailto:paul.hartland at googlemail.com] Sent: Friday, 26 June 2020 8:51 a.m. To: David Emerson Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing This looks like it may be a common problem done a bit of googling not sure if tgis is the same as the link I sent you earlier - https://social.technet.microsoft.com/Forums/security/en-US/eac97768-c388-4b37-8868-829ca4297bfd/nvarcharmax-not-working-with-ado-and-odbc-drivers-other-than-sql-server?forum=sqldataaccess Paul From fuller.artful at gmail.com Mon Jun 29 08:16:00 2020 From: fuller.artful at gmail.com (Arthur Fuller) Date: Mon, 29 Jun 2020 09:16:00 -0400 Subject: [AccessD] Rich Text Field Data from Azure Not Showing In-Reply-To: <011601d64df9$e1ec8d20$a5c5a760$@dalyn.co.nz> References: <00bd01d64795$615d9330$2418b990$@dalyn.co.nz> <00c801d64798$df78df10$9e6a9d30$@dalyn.co.nz> <003201d64806$630f5080$292df180$@dalyn.co.nz> <002001d64aa3$afe03740$0fa0a5c0$@dalyn.co.nz> <003601d64aaf$029c53a0$07d4fae0$@dalyn.co.nz> <004701d64aba$099bdb70$1cd39250$@dalyn.co.nz> <004f01d64aca$7dfa6760$79ef3620$@dalyn.co.nz> <005c01d64ad4$b0b62ea0$12228be0$@dalyn.co.nz> <006401d64ae2$59d25830$0d770890$@dalyn.co.nz> <001701d64b2f$648a7530$2d9f5f90$@dalyn.co.nz> <011601d64df9$e1ec8d20$a5c5a760$@dalyn.co.nz> Message-ID: This is why I love this group! Thanks to this group, I have met many friends from all over the planet (well,,, only a few in physical space, but many over several years in cyberspace. My life is better thanks to all of you. On Mon, Jun 29, 2020 at 5:45 AM David Emerson wrote: > Thanks to the help of this group (especially Paul, Stuart and Jim) we > solved the problem. The solution was to upgrade to version 18 of the OLE > DB Driver and use ?Provider=MSOLEDBSQL? in the connection string. > > > > Regards, David > > > > From: Paul Hartland [mailto:paul.hartland at googlemail.com] > Sent: Friday, 26 June 2020 8:51 a.m. > To: David Emerson > Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing > > > > This looks like it may be a common problem done a bit of googling not sure > if tgis is the same as the link I sent you earlier - > https://social.technet.microsoft.com/Forums/security/en-US/eac97768-c388-4b37-8868-829ca4297bfd/nvarcharmax-not-working-with-ado-and-odbc-drivers-other-than-sql-server?forum=sqldataaccess > > > > Paul > > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > -- Arthur From paul.hartland at googlemail.com Mon Jun 29 08:47:30 2020 From: paul.hartland at googlemail.com (Paul Hartland) Date: Mon, 29 Jun 2020 14:47:30 +0100 Subject: [AccessD] VB6/VBA & OpenOffice - Copy A Range Of Cells From One Sheet To Another Sheet Message-ID: To All, I would be pulling my hair out with this one by now if I hadn't got the clippers on it the weekend, I am trying to copy one range of cells from a selected sheet to another blank sheet and the code below works, so happy days, however it only copies the actual data and not the formatting, anyone ever played with something like this and managed to copy the formatting as well as the data, I have to do it for MS Excel as well, but I think I have code for that somewhere so can't see that being a problem, but this with OpenOffice is driving me insane at the moment. Set objXLOORangeSource = sXLSheetSource.getCellRangeByPosition(lngSourceColStart, lngSourceRowStart, lngSourceColFinsh, lngSourceRowFinish) ' Set target range of cells Set objXLOORangeTarget = objXLOOSheetTarget.getCellRangeByPosition(lngSourceColStart, 0, lngSourceColFinsh, lngTargetRowFinish) objXLOORangeTarget.setDataArray (objXLOORangeSource.getDataArray()) Thanks in advance for any help. -- Paul Hartland paul.hartland at googlemail.com Virus-free. www.avg.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> From jackandpat.d at gmail.com Mon Jun 29 08:50:38 2020 From: jackandpat.d at gmail.com (jack drawbridge) Date: Mon, 29 Jun 2020 09:50:38 -0400 Subject: [AccessD] Rich Text Field Data from Azure Not Showing In-Reply-To: References: <00bd01d64795$615d9330$2418b990$@dalyn.co.nz> <00c801d64798$df78df10$9e6a9d30$@dalyn.co.nz> <003201d64806$630f5080$292df180$@dalyn.co.nz> <002001d64aa3$afe03740$0fa0a5c0$@dalyn.co.nz> <003601d64aaf$029c53a0$07d4fae0$@dalyn.co.nz> <004701d64aba$099bdb70$1cd39250$@dalyn.co.nz> <004f01d64aca$7dfa6760$79ef3620$@dalyn.co.nz> <005c01d64ad4$b0b62ea0$12228be0$@dalyn.co.nz> <006401d64ae2$59d25830$0d770890$@dalyn.co.nz> <001701d64b2f$648a7530$2d9f5f90$@dalyn.co.nz> <011601d64df9$e1ec8d20$a5c5a760$@dalyn.co.nz> Message-ID: 10-4 Arthur! True for most of us I'm sure. Jack On Mon, Jun 29, 2020 at 9:16 AM Arthur Fuller wrote: > This is why I love this group! Thanks to this group, I have met many > friends from all over the planet (well,,, only a few in physical space, but > many over several years in cyberspace. My life is better thanks to all of > you. > > On Mon, Jun 29, 2020 at 5:45 AM David Emerson > wrote: > > > Thanks to the help of this group (especially Paul, Stuart and Jim) we > > solved the problem. The solution was to upgrade to version 18 of the OLE > > DB Driver and use ?Provider=MSOLEDBSQL? in the connection string. > > > > > > > > Regards, David > > > > > > > > From: Paul Hartland [mailto:paul.hartland at googlemail.com] > > Sent: Friday, 26 June 2020 8:51 a.m. > > To: David Emerson > > Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing > > > > > > > > This looks like it may be a common problem done a bit of googling not > sure > > if tgis is the same as the link I sent you earlier - > > > https://social.technet.microsoft.com/Forums/security/en-US/eac97768-c388-4b37-8868-829ca4297bfd/nvarcharmax-not-working-with-ado-and-odbc-drivers-other-than-sql-server?forum=sqldataaccess > > > > > > > > Paul > > > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > > > > -- > Arthur > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > From paul.hartland at googlemail.com Mon Jun 29 09:14:22 2020 From: paul.hartland at googlemail.com (Paul Hartland) Date: Mon, 29 Jun 2020 15:14:22 +0100 Subject: [AccessD] Rich Text Field Data from Azure Not Showing In-Reply-To: References: <00bd01d64795$615d9330$2418b990$@dalyn.co.nz> <00c801d64798$df78df10$9e6a9d30$@dalyn.co.nz> <003201d64806$630f5080$292df180$@dalyn.co.nz> <002001d64aa3$afe03740$0fa0a5c0$@dalyn.co.nz> <003601d64aaf$029c53a0$07d4fae0$@dalyn.co.nz> <004701d64aba$099bdb70$1cd39250$@dalyn.co.nz> <004f01d64aca$7dfa6760$79ef3620$@dalyn.co.nz> <005c01d64ad4$b0b62ea0$12228be0$@dalyn.co.nz> <006401d64ae2$59d25830$0d770890$@dalyn.co.nz> <001701d64b2f$648a7530$2d9f5f90$@dalyn.co.nz> <011601d64df9$e1ec8d20$a5c5a760$@dalyn.co.nz> Message-ID: Has anyone saw a question I sent to the list about 15 minutes ago ? I haven't seen it pop up yet. Paul On Mon, 29 Jun 2020, 14:51 jack drawbridge, wrote: > 10-4 Arthur! True for most of us I'm sure. > Jack > > On Mon, Jun 29, 2020 at 9:16 AM Arthur Fuller > wrote: > > > This is why I love this group! Thanks to this group, I have met many > > friends from all over the planet (well,,, only a few in physical space, > but > > many over several years in cyberspace. My life is better thanks to all of > > you. > > > > On Mon, Jun 29, 2020 at 5:45 AM David Emerson > > wrote: > > > > > Thanks to the help of this group (especially Paul, Stuart and Jim) we > > > solved the problem. The solution was to upgrade to version 18 of the > OLE > > > DB Driver and use ?Provider=MSOLEDBSQL? in the connection string. > > > > > > > > > > > > Regards, David > > > > > > > > > > > > From: Paul Hartland [mailto:paul.hartland at googlemail.com] > > > Sent: Friday, 26 June 2020 8:51 a.m. > > > To: David Emerson > > > Subject: Re: [AccessD] Rich Text Field Data from Azure Not Showing > > > > > > > > > > > > This looks like it may be a common problem done a bit of googling not > > sure > > > if tgis is the same as the link I sent you earlier - > > > > > > https://social.technet.microsoft.com/Forums/security/en-US/eac97768-c388-4b37-8868-829ca4297bfd/nvarcharmax-not-working-with-ado-and-odbc-drivers-other-than-sql-server?forum=sqldataaccess > > > > > > > > > > > > Paul > > > > > > -- > > > AccessD mailing list > > > AccessD at databaseadvisors.com > > > http://databaseadvisors.com/mailman/listinfo/accessd > > > Website: http://www.databaseadvisors.com > > > > > > > > > -- > > Arthur > > -- > > 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 Mon Jun 29 10:16:59 2020 From: df.waters at outlook.com (Daniel Waters) Date: Mon, 29 Jun 2020 15:16:59 +0000 Subject: [AccessD] VB6/VBA & OpenOffice - Copy A Range Of Cells From One Sheet To Another Sheet In-Reply-To: References: Message-ID: Hi Paul, Something to try -- In Excel, you can record a macro, then view the code recorded. That macro code can then be manipulated in the VBA window to turn it into what you actually want. I used this technique a lot in the past and could not have manipulated Excel from Access if I hadn't. Start a Macro. Type anything into a cell. Format that cell in some way. Right-click that cell and select Copy. Right-click a different cell and you'll see some Paste Options. Hover over Paste Special and a window appears. Then hover over the icon in the top row on the right where the pop-up says, 'Keep Source Formatting.' Left-click on that icon (it looks like a clipboard with a sheet of paper with lines of text). End the Macro Now you can open and view the Macro in edit mode where you can see the code step by step. Hopefully, some of that code specifically shows how to keep the source formatting. Unfortunately, I can't get into edit mode for Macros on my PC. Excel tries to open Visual Studio as the code editing software (and then stalls out) instead of the VBA editor in Excel. Did a google search on this issue and couldn't find anyone else who has the same problem! Good Luck! Dan -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Paul Hartland via AccessD Sent: Monday, June 29, 2020 8:48 AM To: Access List Cc: Paul Hartland Subject: [AccessD] VB6/VBA & OpenOffice - Copy A Range Of Cells From One Sheet To Another Sheet To All, I would be pulling my hair out with this one by now if I hadn't got the clippers on it the weekend, I am trying to copy one range of cells from a selected sheet to another blank sheet and the code below works, so happy days, however it only copies the actual data and not the formatting, anyone ever played with something like this and managed to copy the formatting as well as the data, I have to do it for MS Excel as well, but I think I have code for that somewhere so can't see that being a problem, but this with OpenOffice is driving me insane at the moment. Set objXLOORangeSource = sXLSheetSource.getCellRangeByPosition(lngSourceColStart, lngSourceRowStart, lngSourceColFinsh, lngSourceRowFinish) ' Set target range of cells Set objXLOORangeTarget = objXLOOSheetTarget.getCellRangeByPosition(lngSourceColStart, 0, lngSourceColFinsh, lngTargetRowFinish) objXLOORangeTarget.setDataArray (objXLOORangeSource.getDataArray()) Thanks in advance for any help. -- Paul Hartland paul.hartland at googlemail.com Virus-free. www.avg.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com From df.waters at outlook.com Mon Jun 29 10:20:26 2020 From: df.waters at outlook.com (Daniel Waters) Date: Mon, 29 Jun 2020 15:20:26 +0000 Subject: [AccessD] VB6/VBA & OpenOffice - Copy A Range Of Cells From One Sheet To Another Sheet In-Reply-To: References: Message-ID: Maybe OpenOffice can also let you record a macro? -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Daniel Waters Sent: Monday, June 29, 2020 10:17 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] VB6/VBA & OpenOffice - Copy A Range Of Cells From One Sheet To Another Sheet Hi Paul, Something to try -- In Excel, you can record a macro, then view the code recorded. That macro code can then be manipulated in the VBA window to turn it into what you actually want. I used this technique a lot in the past and could not have manipulated Excel from Access if I hadn't. Start a Macro. Type anything into a cell. Format that cell in some way. Right-click that cell and select Copy. Right-click a different cell and you'll see some Paste Options. Hover over Paste Special and a window appears. Then hover over the icon in the top row on the right where the pop-up says, 'Keep Source Formatting.' Left-click on that icon (it looks like a clipboard with a sheet of paper with lines of text). End the Macro Now you can open and view the Macro in edit mode where you can see the code step by step. Hopefully, some of that code specifically shows how to keep the source formatting. Unfortunately, I can't get into edit mode for Macros on my PC. Excel tries to open Visual Studio as the code editing software (and then stalls out) instead of the VBA editor in Excel. Did a google search on this issue and couldn't find anyone else who has the same problem! Good Luck! Dan -----Original Message----- From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Paul Hartland via AccessD Sent: Monday, June 29, 2020 8:48 AM To: Access List Cc: Paul Hartland Subject: [AccessD] VB6/VBA & OpenOffice - Copy A Range Of Cells From One Sheet To Another Sheet To All, I would be pulling my hair out with this one by now if I hadn't got the clippers on it the weekend, I am trying to copy one range of cells from a selected sheet to another blank sheet and the code below works, so happy days, however it only copies the actual data and not the formatting, anyone ever played with something like this and managed to copy the formatting as well as the data, I have to do it for MS Excel as well, but I think I have code for that somewhere so can't see that being a problem, but this with OpenOffice is driving me insane at the moment. Set objXLOORangeSource = sXLSheetSource.getCellRangeByPosition(lngSourceColStart, lngSourceRowStart, lngSourceColFinsh, lngSourceRowFinish) ' Set target range of cells Set objXLOORangeTarget = objXLOOSheetTarget.getCellRangeByPosition(lngSourceColStart, 0, lngSourceColFinsh, lngTargetRowFinish) objXLOORangeTarget.setDataArray (objXLOORangeSource.getDataArray()) Thanks in advance for any help. -- Paul Hartland paul.hartland at googlemail.com Virus-free. www.avg.com <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> -- 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 paul.hartland at googlemail.com Mon Jun 29 11:03:34 2020 From: paul.hartland at googlemail.com (Paul Hartland) Date: Mon, 29 Jun 2020 17:03:34 +0100 Subject: [AccessD] VB6/VBA & OpenOffice - Copy A Range Of Cells From One Sheet To Another Sheet In-Reply-To: References: Message-ID: Thanks Dan, thats what I usually do when stuck with Excel, but doesnt seem to be the same with open office which I am stuck on, but thank you anyway :) Paul On Mon, 29 Jun 2020, 16:17 Daniel Waters, wrote: > Hi Paul, > > Something to try -- > > In Excel, you can record a macro, then view the code recorded. That macro > code can then be manipulated in the VBA window to turn it into what you > actually want. I used this technique a lot in the past and could not have > manipulated Excel from Access if I hadn't. > > Start a Macro. > > Type anything into a cell. > Format that cell in some way. > Right-click that cell and select Copy. > Right-click a different cell and you'll see some Paste Options. > Hover over Paste Special and a window appears. > Then hover over the icon in the top row on the right where the pop-up > says, 'Keep Source Formatting.' > Left-click on that icon (it looks like a clipboard with a sheet of paper > with lines of text). > > End the Macro > > Now you can open and view the Macro in edit mode where you can see the > code step by step. Hopefully, some of that code specifically shows how to > keep the source formatting. > > Unfortunately, I can't get into edit mode for Macros on my PC. Excel > tries to open Visual Studio as the code editing software (and then stalls > out) instead of the VBA editor in Excel. Did a google search on this issue > and couldn't find anyone else who has the same problem! > > Good Luck! > Dan > > > -----Original Message----- > From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of > Paul Hartland via AccessD > Sent: Monday, June 29, 2020 8:48 AM > To: Access List > Cc: Paul Hartland > Subject: [AccessD] VB6/VBA & OpenOffice - Copy A Range Of Cells From One > Sheet To Another Sheet > > To All, > > I would be pulling my hair out with this one by now if I hadn't got the > clippers on it the weekend, I am trying to copy one range of cells from a > selected sheet to another blank sheet and the code below works, so happy > days, however it only copies the actual data and not the formatting, anyone > ever played with something like this and managed to copy the formatting as > well as the data, I have to do it for MS Excel as well, but I think I have > code for that somewhere so can't see that being a problem, but this with > OpenOffice is driving me insane at the moment. > > Set objXLOORangeSource = > sXLSheetSource.getCellRangeByPosition(lngSourceColStart, lngSourceRowStart, > lngSourceColFinsh, lngSourceRowFinish) > ' Set target range of cells > Set objXLOORangeTarget = > objXLOOSheetTarget.getCellRangeByPosition(lngSourceColStart, 0, > lngSourceColFinsh, lngTargetRowFinish) > objXLOORangeTarget.setDataArray (objXLOORangeSource.getDataArray()) > > Thanks in advance for any help. > > > -- > Paul Hartland > paul.hartland at googlemail.com > > < > http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail > > > Virus-free. > www.avg.com > < > http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail > > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > -- > 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 paul.hartland at googlemail.com Tue Jun 30 09:02:02 2020 From: paul.hartland at googlemail.com (Paul Hartland) Date: Tue, 30 Jun 2020 15:02:02 +0100 Subject: [AccessD] VB6/VBA & OpenOffice - Copy A Range Of Cells From One Sheet To Another Sheet In-Reply-To: References: Message-ID: Got the solution to this now for both open office and Excel Paul On Mon, 29 Jun 2020, 17:03 Paul Hartland, wrote: > Thanks Dan, thats what I usually do when stuck with Excel, but doesnt seem > to be the same with open office which I am stuck on, but thank you anyway :) > > Paul > > On Mon, 29 Jun 2020, 16:17 Daniel Waters, wrote: > >> Hi Paul, >> >> Something to try -- >> >> In Excel, you can record a macro, then view the code recorded. That >> macro code can then be manipulated in the VBA window to turn it into what >> you actually want. I used this technique a lot in the past and could not >> have manipulated Excel from Access if I hadn't. >> >> Start a Macro. >> >> Type anything into a cell. >> Format that cell in some way. >> Right-click that cell and select Copy. >> Right-click a different cell and you'll see some Paste Options. >> Hover over Paste Special and a window appears. >> Then hover over the icon in the top row on the right where the pop-up >> says, 'Keep Source Formatting.' >> Left-click on that icon (it looks like a clipboard with a sheet of paper >> with lines of text). >> >> End the Macro >> >> Now you can open and view the Macro in edit mode where you can see the >> code step by step. Hopefully, some of that code specifically shows how to >> keep the source formatting. >> >> Unfortunately, I can't get into edit mode for Macros on my PC. Excel >> tries to open Visual Studio as the code editing software (and then stalls >> out) instead of the VBA editor in Excel. Did a google search on this issue >> and couldn't find anyone else who has the same problem! >> >> Good Luck! >> Dan >> >> >> -----Original Message----- >> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of >> Paul Hartland via AccessD >> Sent: Monday, June 29, 2020 8:48 AM >> To: Access List >> Cc: Paul Hartland >> Subject: [AccessD] VB6/VBA & OpenOffice - Copy A Range Of Cells From One >> Sheet To Another Sheet >> >> To All, >> >> I would be pulling my hair out with this one by now if I hadn't got the >> clippers on it the weekend, I am trying to copy one range of cells from a >> selected sheet to another blank sheet and the code below works, so happy >> days, however it only copies the actual data and not the formatting, >> anyone >> ever played with something like this and managed to copy the formatting as >> well as the data, I have to do it for MS Excel as well, but I think I have >> code for that somewhere so can't see that being a problem, but this with >> OpenOffice is driving me insane at the moment. >> >> Set objXLOORangeSource = >> sXLSheetSource.getCellRangeByPosition(lngSourceColStart, >> lngSourceRowStart, >> lngSourceColFinsh, lngSourceRowFinish) >> ' Set target range of cells >> Set objXLOORangeTarget = >> objXLOOSheetTarget.getCellRangeByPosition(lngSourceColStart, 0, >> lngSourceColFinsh, lngTargetRowFinish) >> objXLOORangeTarget.setDataArray (objXLOORangeSource.getDataArray()) >> >> Thanks in advance for any help. >> >> >> -- >> Paul Hartland >> paul.hartland at googlemail.com >> >> < >> http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail >> > >> Virus-free. >> www.avg.com >> < >> http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail >> > >> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >> -- >> 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 >> >