[AccessD] Nvarchar(max)

Ryan W wrwehler at gmail.com
Fri Jul 2 07:48:49 CDT 2021


I do seem to remember either a bug or suggestion to not use 4000 on
NVARCHAR once upon a time.  If assumption was it is a bug and many years
ago I'd think it would have been fixed by now.






On Fri, Jul 2, 2021 at 2:05 AM Anita Smith <anita at ddisolutions.com.au>
wrote:

> I will try with various values and report back.
>
>
>
>
> Anita Smith
>
> [cid:DDi-Solutions-Email-Logo_fdcff211-839d-4fd1-865e-c500dea56b8a.png]<
> www.ddisolutions.com.au>        M: 0402 022 462
> E: anita at ddisolutions.com.au<mailto:anita at ddisolutions.com.au>
> Custom Software, Databases and Websites
> P Please consider the environment before printing this email.
> The content of this message is confidential. If you have received it by
> mistake, please inform us by an email reply and then delete the message. It
> is forbidden to copy, forward, or in any way reveal the contents of this
> message to anyone. The integrity and security of this email cannot be
> guaranteed over the Internet. Therefore, the sender will not be held liable
> for any damage caused by the message.
>
> -------- Original message --------
> From: Gustav Brock via AccessD <accessd at databaseadvisors.com>
> Date: 2/7/21 16:43 (GMT+10:00)
> To: Access Developers discussion and problem solving <
> accessd at databaseadvisors.com>
> Cc: Gustav Brock <gustav at cactus.dk>
> Subject: Re: [AccessD] Nvarchar(max)
>
> Hi Anita
>
> A second thought: Is it only the use of max in nvarchar(max) that exposes
> the issue, or would any value of n in nvarchar(n) larger than some value
> also expose the issue?
>
> /gustav
>
> -----Oprindelig meddelelse-----
> Fra: AccessD <accessd-bounces+gustav=cactus.dk at databaseadvisors.com> På
> vegne af Anita Smith
> Sendt: 2. juli 2021 08:12
> Til: Access Developers discussion and problem solving <
> accessd at databaseadvisors.com>
> Emne: Re: [AccessD] Nvarchar(max)
>
> Gustav,
> I have cracked open a new day and with it, a clearer head.
>
> These are my findings:
>
> Long story short - no matter the versions of Access and SQL server the
> nvarchar(max) issue persisted and always went away if I changed the field
> size to nvarchar(1000).
>
> <snip>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


More information about the AccessD mailing list