From fuller.artful at gmail.com  Wed Dec  1 12:10:21 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Wed, 1 Dec 2021 13:10:21 -0500
Subject: [AccessD] Small Google Calendar question
Message-ID: <CAEPJO1hTOc5mx0x4nu2SYdLHx18+Mgm9szsbk2udrQx_7DbZjA@mail.gmail.com>

For some reason, Calendar always opens at October of this year. even if I
jump to today, close it and re-open it, it opens at October. Any way to
make it open at Today?

-- 
Arthur

From garykjos at gmail.com  Wed Dec  1 12:29:42 2021
From: garykjos at gmail.com (Gary Kjos)
Date: Wed, 1 Dec 2021 12:29:42 -0600
Subject: [AccessD] Small Google Calendar question
In-Reply-To: <CAEPJO1hTOc5mx0x4nu2SYdLHx18+Mgm9szsbk2udrQx_7DbZjA@mail.gmail.com>
References: <CAEPJO1hTOc5mx0x4nu2SYdLHx18+Mgm9szsbk2udrQx_7DbZjA@mail.gmail.com>
Message-ID: <CAJ2R_p+KekNguU4Rm-tozUy3OONvFp-nKNvF74VueHa_qM4RCw@mail.gmail.com>

Are you opening it from a shortcut or bookmark?

Perhaps your shortcut or link is tied to a specific date.  Set the
link to a non-specific pointer

https://calendar.google.com


On Wed, Dec 1, 2021 at 12:10 PM Arthur Fuller <fuller.artful at gmail.com> wrote:
>
> For some reason, Calendar always opens at October of this year. even if I
> jump to today, close it and re-open it, it opens at October. Any way to
> make it open at Today?
>
> --
> Arthur
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com



-- 
Gary Kjos
garykjos at gmail.com

From fuller.artful at gmail.com  Wed Dec  1 13:41:23 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Wed, 1 Dec 2021 14:41:23 -0500
Subject: [AccessD] Small Google Calendar question
In-Reply-To: <CAJ2R_p+KekNguU4Rm-tozUy3OONvFp-nKNvF74VueHa_qM4RCw@mail.gmail.com>
References: <CAEPJO1hTOc5mx0x4nu2SYdLHx18+Mgm9szsbk2udrQx_7DbZjA@mail.gmail.com>
 <CAJ2R_p+KekNguU4Rm-tozUy3OONvFp-nKNvF74VueHa_qM4RCw@mail.gmail.com>
Message-ID: <CAEPJO1j-UPSfx89tBSL4rN9TK-MbMS=oPO7rG56BtS9gqRmV2w@mail.gmail.com>

Thanks, Gary, I'll give that a try. Side question. I have occasionally
puzzled over how to pronounce your surname.  My best guess is kee-yoss, but
that's as good as it gets, guess-wise. Another puzzle is the pronunciation
of Borge's given name. When I see his signature, I two things come
immediately to mind: Victore Borge, the pianist/comedian, and Jrges Luis
Borges
Side question

On Wed, Dec 1, 2021 at 1:30 PM Gary Kjos <garykjos at gmail.com> wrote:

> Are you opening it from a shortcut or bookmark?
>
> Perhaps your shortcut or link is tied to a specific date.  Set the
> link to a non-specific pointer
>
> https://calendar.google.com
>
>
> On Wed, Dec 1, 2021 at 12:10 PM Arthur Fuller <fuller.artful at gmail.com>
> wrote:
> >
> > For some reason, Calendar always opens at October of this year. even if I
> > jump to today, close it and re-open it, it opens at October. Any way to
> > make it open at Today?
> >
> > --
> > Arthur
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
>
>
>
> --
> Gary Kjos
> garykjos at gmail.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
Arthur

From bensonforums at gmail.com  Wed Dec  1 13:45:06 2021
From: bensonforums at gmail.com (Bill Benson)
Date: Wed, 1 Dec 2021 14:45:06 -0500
Subject: [AccessD] Small Google Calendar question
In-Reply-To: <CAEPJO1j-UPSfx89tBSL4rN9TK-MbMS=oPO7rG56BtS9gqRmV2w@mail.gmail.com>
References: <CAEPJO1hTOc5mx0x4nu2SYdLHx18+Mgm9szsbk2udrQx_7DbZjA@mail.gmail.com>
 <CAJ2R_p+KekNguU4Rm-tozUy3OONvFp-nKNvF74VueHa_qM4RCw@mail.gmail.com>
 <CAEPJO1j-UPSfx89tBSL4rN9TK-MbMS=oPO7rG56BtS9gqRmV2w@mail.gmail.com>
Message-ID: <CAJLzs_2zrAweqnpwdCTYo+hDMibgD7cZ3KXGVGsL+MdksOZjSw@mail.gmail.com>

how to pronounce [Gary's] surname

Can we have a competition?

On Wed, Dec 1, 2021 at 2:41 PM Arthur Fuller <fuller.artful at gmail.com>
wrote:

> Thanks, Gary, I'll give that a try. Side question. I have occasionally
> puzzled over how to pronounce your surname.  My best guess is kee-yoss, but
> that's as good as it gets, guess-wise. Another puzzle is the pronunciation
> of Borge's given name. When I see his signature, I two things come
> immediately to mind: Victore Borge, the pianist/comedian, and Jrges Luis
> Borges
> Side question
>
> On Wed, Dec 1, 2021 at 1:30 PM Gary Kjos <garykjos at gmail.com> wrote:
>
> > Are you opening it from a shortcut or bookmark?
> >
> > Perhaps your shortcut or link is tied to a specific date.  Set the
> > link to a non-specific pointer
> >
> > https://calendar.google.com
> >
> >
> > On Wed, Dec 1, 2021 at 12:10 PM Arthur Fuller <fuller.artful at gmail.com>
> > wrote:
> > >
> > > For some reason, Calendar always opens at October of this year. even
> if I
> > > jump to today, close it and re-open it, it opens at October. Any way to
> > > make it open at Today?
> > >
> > > --
> > > Arthur
> > > --
> > > AccessD mailing list
> > > AccessD at databaseadvisors.com
> > > https://databaseadvisors.com/mailman/listinfo/accessd
> > > Website: http://www.databaseadvisors.com
> >
> >
> >
> > --
> > Gary Kjos
> > garykjos at gmail.com
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
>
>
> --
> Arthur
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From bensonforums at gmail.com  Wed Dec  1 13:46:05 2021
From: bensonforums at gmail.com (Bill Benson)
Date: Wed, 1 Dec 2021 14:46:05 -0500
Subject: [AccessD] Small Google Calendar question
In-Reply-To: <CAJLzs_2zrAweqnpwdCTYo+hDMibgD7cZ3KXGVGsL+MdksOZjSw@mail.gmail.com>
References: <CAEPJO1hTOc5mx0x4nu2SYdLHx18+Mgm9szsbk2udrQx_7DbZjA@mail.gmail.com>
 <CAJ2R_p+KekNguU4Rm-tozUy3OONvFp-nKNvF74VueHa_qM4RCw@mail.gmail.com>
 <CAEPJO1j-UPSfx89tBSL4rN9TK-MbMS=oPO7rG56BtS9gqRmV2w@mail.gmail.com>
 <CAJLzs_2zrAweqnpwdCTYo+hDMibgD7cZ3KXGVGsL+MdksOZjSw@mail.gmail.com>
Message-ID: <CAJLzs_0LEL7oP-=spLdEetFDNYZyarw+m9pm7TCJHTv3XWkSFw@mail.gmail.com>

If so I have cheated
https://www.howtopronounce.com/norwegian/kjos

On Wed, Dec 1, 2021 at 2:45 PM Bill Benson <bensonforums at gmail.com> wrote:

> how to pronounce [Gary's] surname
>
> Can we have a competition?
>
> On Wed, Dec 1, 2021 at 2:41 PM Arthur Fuller <fuller.artful at gmail.com>
> wrote:
>
>> Thanks, Gary, I'll give that a try. Side question. I have occasionally
>> puzzled over how to pronounce your surname.  My best guess is kee-yoss,
>> but
>> that's as good as it gets, guess-wise. Another puzzle is the pronunciation
>> of Borge's given name. When I see his signature, I two things come
>> immediately to mind: Victore Borge, the pianist/comedian, and Jrges Luis
>> Borges
>> Side question
>>
>> On Wed, Dec 1, 2021 at 1:30 PM Gary Kjos <garykjos at gmail.com> wrote:
>>
>> > Are you opening it from a shortcut or bookmark?
>> >
>> > Perhaps your shortcut or link is tied to a specific date.  Set the
>> > link to a non-specific pointer
>> >
>> > https://calendar.google.com
>> >
>> >
>> > On Wed, Dec 1, 2021 at 12:10 PM Arthur Fuller <fuller.artful at gmail.com>
>> > wrote:
>> > >
>> > > For some reason, Calendar always opens at October of this year. even
>> if I
>> > > jump to today, close it and re-open it, it opens at October. Any way
>> to
>> > > make it open at Today?
>> > >
>> > > --
>> > > Arthur
>> > > --
>> > > AccessD mailing list
>> > > AccessD at databaseadvisors.com
>> > > https://databaseadvisors.com/mailman/listinfo/accessd
>> > > Website: http://www.databaseadvisors.com
>> >
>> >
>> >
>> > --
>> > Gary Kjos
>> > garykjos at gmail.com
>> > --
>> > AccessD mailing list
>> > AccessD at databaseadvisors.com
>> > https://databaseadvisors.com/mailman/listinfo/accessd
>> > Website: http://www.databaseadvisors.com
>> >
>>
>>
>> --
>> Arthur
>> --
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> https://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com
>>
>

From fuller.artful at gmail.com  Wed Dec  1 14:12:44 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Wed, 1 Dec 2021 15:12:44 -0500
Subject: [AccessD] Small Google Calendar question
In-Reply-To: <CAJLzs_2zrAweqnpwdCTYo+hDMibgD7cZ3KXGVGsL+MdksOZjSw@mail.gmail.com>
References: <CAEPJO1hTOc5mx0x4nu2SYdLHx18+Mgm9szsbk2udrQx_7DbZjA@mail.gmail.com>
 <CAJ2R_p+KekNguU4Rm-tozUy3OONvFp-nKNvF74VueHa_qM4RCw@mail.gmail.com>
 <CAEPJO1j-UPSfx89tBSL4rN9TK-MbMS=oPO7rG56BtS9gqRmV2w@mail.gmail.com>
 <CAJLzs_2zrAweqnpwdCTYo+hDMibgD7cZ3KXGVGsL+MdksOZjSw@mail.gmail.com>
Message-ID: <CAEPJO1g+WO6JH2zAHvXZVQnBTdZ6Fkg9AOD496R+ajrz1bxsPQ@mail.gmail.com>

I am going to guess "kiosk" but without the K, almost like Chaos.

On Wed, Dec 1, 2021 at 2:45 PM Bill Benson <bensonforums at gmail.com> wrote:

> how to pronounce [Gary's] surname
>
> Can we have a competition?
>
> On Wed, Dec 1, 2021 at 2:41 PM Arthur Fuller <fuller.artful at gmail.com>
> wrote:
>
> > Thanks, Gary, I'll give that a try. Side question. I have occasionally
> > puzzled over how to pronounce your surname.  My best guess is kee-yoss,
> but
> > that's as good as it gets, guess-wise. Another puzzle is the
> pronunciation
> > of Borge's given name. When I see his signature, I two things come
> > immediately to mind: Victore Borge, the pianist/comedian, and Jrges Luis
> > Borges
> > Side question
> >
> > On Wed, Dec 1, 2021 at 1:30 PM Gary Kjos <garykjos at gmail.com> wrote:
> >
> > > Are you opening it from a shortcut or bookmark?
> > >
> > > Perhaps your shortcut or link is tied to a specific date.  Set the
> > > link to a non-specific pointer
> > >
> > > https://calendar.google.com
> > >
> > >
> > > On Wed, Dec 1, 2021 at 12:10 PM Arthur Fuller <fuller.artful at gmail.com
> >
> > > wrote:
> > > >
> > > > For some reason, Calendar always opens at October of this year. even
> > if I
> > > > jump to today, close it and re-open it, it opens at October. Any way
> to
> > > > make it open at Today?
> > > >
> > > > --
> > > > Arthur
> > > > --
> > > > AccessD mailing list
> > > > AccessD at databaseadvisors.com
> > > > https://databaseadvisors.com/mailman/listinfo/accessd
> > > > Website: http://www.databaseadvisors.com
> > >
> > >
> > >
> > > --
> > > Gary Kjos
> > > garykjos at gmail.com
> > > --
> > > AccessD mailing list
> > > AccessD at databaseadvisors.com
> > > https://databaseadvisors.com/mailman/listinfo/accessd
> > > Website: http://www.databaseadvisors.com
> > >
> >
> >
> > --
> > Arthur
> > --
> > 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
>


-- 
Arthur

From pcs.accessd at gmail.com  Wed Dec  1 15:20:39 2021
From: pcs.accessd at gmail.com (Borge Hansen)
Date: Thu, 2 Dec 2021 07:20:39 +1000
Subject: [AccessD] How to handle orphaned group header / footer
In-Reply-To: <61A47C24.2510.27D1F9D6@stuart.lexacorp.com.pg>
References: <CAF+SPM_ZS1SXPgF=ESPqskE-9Y+AJXzVKhow4F99m2M+jBoG=Q@mail.gmail.com>
 <61A47C24.2510.27D1F9D6@stuart.lexacorp.com.pg>
Message-ID: <CAF+SPM-P+kXFyPU7FpsY6XXCgCBMdE5sC1fKngixo9_eV8U9nQ@mail.gmail.com>

Well, what I did was to change the report record source back to using
the original table name instead of the table alias. This enabled me to
remove the group header and footer from the Group/Sort dialog list.
Then changing the sql record source back to using the table alias I
inserted the group header and footer this time reflecting the table
alias (two joins to the same table therefore the need for the table /
alias prefix).
/borge

On Mon, Nov 29, 2021 at 5:07 PM Stuart McLachlan <stuart at lexacorp.com.pg> wrote:
>
> Have you tried changing the report Recordsource to a different query and then changing it
> back again (saving between changes)  That should refresh the  Group/Sort dialog field list.
>
> The old Group fieldname may be changed  to "Expression:", but you should be able to
> update that to the new field name.
>
> On 29 Nov 2021 at 14:46, Borge Hansen wrote:
>
> > Hello everyone,
> >
> > This relates to a report that was created way back in Access2003.
> > I have since changed the underlying query table aliases for the report query.
> >
> > The report used to handle this group header / footer (referred to in
> > the property sheet as GroupHeader2 and GroupFooter4):
> > tblContactWasReferredBy.FullNameSorting Header / Footer
> >
> > After having changed the report query table aliases we are now dealing with:
> > crb.FullNameSorting Header / Footer
> >
> > Because I changed the table alias to crb, the group old header /
> > footer does not appear in the "Grouping Dialog Box" ... and I cannot
> > delete the header/footer from within the "Grouping Dialog Box".
> >
> > I can't find a way to remove this "orphaned" group header and footer,
> > other than revert the report query to the original table name instead
> > of the table alias.
> >
> > Is there a way - through VBA - to remove such 'orphaned' group headers
> > and footers as these "GroupHeader2" and "GroupFooter4" or whatever the
> > case may be?
> >
> > /borge
> > --
> > 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

From garykjos at gmail.com  Wed Dec  1 17:10:50 2021
From: garykjos at gmail.com (Gary Kjos)
Date: Wed, 1 Dec 2021 17:10:50 -0600
Subject: [AccessD] Small Google Calendar question
In-Reply-To: <CAJLzs_0LEL7oP-=spLdEetFDNYZyarw+m9pm7TCJHTv3XWkSFw@mail.gmail.com>
References: <CAEPJO1hTOc5mx0x4nu2SYdLHx18+Mgm9szsbk2udrQx_7DbZjA@mail.gmail.com>
 <CAJ2R_p+KekNguU4Rm-tozUy3OONvFp-nKNvF74VueHa_qM4RCw@mail.gmail.com>
 <CAEPJO1j-UPSfx89tBSL4rN9TK-MbMS=oPO7rG56BtS9gqRmV2w@mail.gmail.com>
 <CAJLzs_2zrAweqnpwdCTYo+hDMibgD7cZ3KXGVGsL+MdksOZjSw@mail.gmail.com>
 <CAJLzs_0LEL7oP-=spLdEetFDNYZyarw+m9pm7TCJHTv3XWkSFw@mail.gmail.com>
Message-ID: <CAJ2R_pLVE3GGibOzc+Ai_y=ZKmMW2UDsfFpcRouQWtjB6+NwrQ@mail.gmail.com>

That's close Bill.  My family has always said CH like Chair and OSE
like Close.  So chose.  I've also used a SILENT K explanation.

I spell it a lot.

GK

On Wed, Dec 1, 2021 at 1:46 PM Bill Benson <bensonforums at gmail.com> wrote:
>
> If so I have cheated
> https://www.howtopronounce.com/norwegian/kjos
>
> On Wed, Dec 1, 2021 at 2:45 PM Bill Benson <bensonforums at gmail.com> wrote:
>
> > how to pronounce [Gary's] surname
> >
> > Can we have a competition?
> >
> > On Wed, Dec 1, 2021 at 2:41 PM Arthur Fuller <fuller.artful at gmail.com>
> > wrote:
> >
> >> Thanks, Gary, I'll give that a try. Side question. I have occasionally
> >> puzzled over how to pronounce your surname.  My best guess is kee-yoss,
> >> but
> >> that's as good as it gets, guess-wise. Another puzzle is the pronunciation
> >> of Borge's given name. When I see his signature, I two things come
> >> immediately to mind: Victore Borge, the pianist/comedian, and Jrges Luis
> >> Borges
> >> Side question
> >>
> >> On Wed, Dec 1, 2021 at 1:30 PM Gary Kjos <garykjos at gmail.com> wrote:
> >>
> >> > Are you opening it from a shortcut or bookmark?
> >> >
> >> > Perhaps your shortcut or link is tied to a specific date.  Set the
> >> > link to a non-specific pointer
> >> >
> >> > https://calendar.google.com
> >> >
> >> >
> >> > On Wed, Dec 1, 2021 at 12:10 PM Arthur Fuller <fuller.artful at gmail.com>
> >> > wrote:
> >> > >
> >> > > For some reason, Calendar always opens at October of this year. even
> >> if I
> >> > > jump to today, close it and re-open it, it opens at October. Any way
> >> to
> >> > > make it open at Today?
> >> > >
> >> > > --
> >> > > Arthur
> >> > > --
> >> > > AccessD mailing list
> >> > > AccessD at databaseadvisors.com
> >> > > https://databaseadvisors.com/mailman/listinfo/accessd
> >> > > Website: http://www.databaseadvisors.com
> >> >
> >> >
> >> >
> >> > --
> >> > Gary Kjos
> >> > garykjos at gmail.com
> >> > --
> >> > AccessD mailing list
> >> > AccessD at databaseadvisors.com
> >> > https://databaseadvisors.com/mailman/listinfo/accessd
> >> > Website: http://www.databaseadvisors.com
> >> >
> >>
> >>
> >> --
> >> Arthur
> >> --
> >> 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



-- 
Gary Kjos
garykjos at gmail.com

From garykjos at gmail.com  Wed Dec  1 17:10:59 2021
From: garykjos at gmail.com (Gary Kjos)
Date: Wed, 1 Dec 2021 17:10:59 -0600
Subject: [AccessD] Small Google Calendar question
In-Reply-To: <CAEPJO1g+WO6JH2zAHvXZVQnBTdZ6Fkg9AOD496R+ajrz1bxsPQ@mail.gmail.com>
References: <CAEPJO1hTOc5mx0x4nu2SYdLHx18+Mgm9szsbk2udrQx_7DbZjA@mail.gmail.com>
 <CAJ2R_p+KekNguU4Rm-tozUy3OONvFp-nKNvF74VueHa_qM4RCw@mail.gmail.com>
 <CAEPJO1j-UPSfx89tBSL4rN9TK-MbMS=oPO7rG56BtS9gqRmV2w@mail.gmail.com>
 <CAJLzs_2zrAweqnpwdCTYo+hDMibgD7cZ3KXGVGsL+MdksOZjSw@mail.gmail.com>
 <CAEPJO1g+WO6JH2zAHvXZVQnBTdZ6Fkg9AOD496R+ajrz1bxsPQ@mail.gmail.com>
Message-ID: <CAJ2R_pJp+DeCnjUkkzisfhY4BRw+EnzxKJV26BjLLxk32H5JJw@mail.gmail.com>

RE: Pronouncing Kjos.

I spell my name a lot.  Pretty much every time I need to give it.
Probably at least twice most times.

My family pronounces it with a CH sound.  Like the "Ch" in Chair at
the beginning and like the "ose" in close on the back.  So Chose is an
approximation. Throughout my school days I told people it was a silent
K.  So just Jose

My brother's buddies all call him Ka-Jose with two syllables.

When I was introduced to some friends of friends for a golfing outing,
the newly met people called me Juice.

Thanks for asking.

On Wed, Dec 1, 2021 at 2:13 PM Arthur Fuller <fuller.artful at gmail.com> wrote:
>
> I am going to guess "kiosk" but without the K, almost like Chaos.
>
> On Wed, Dec 1, 2021 at 2:45 PM Bill Benson <bensonforums at gmail.com> wrote:
>
> > how to pronounce [Gary's] surname
> >
> > Can we have a competition?
> >
> > On Wed, Dec 1, 2021 at 2:41 PM Arthur Fuller <fuller.artful at gmail.com>
> > wrote:
> >
> > > Thanks, Gary, I'll give that a try. Side question. I have occasionally
> > > puzzled over how to pronounce your surname.  My best guess is kee-yoss,
> > but
> > > that's as good as it gets, guess-wise. Another puzzle is the
> > pronunciation
> > > of Borge's given name. When I see his signature, I two things come
> > > immediately to mind: Victore Borge, the pianist/comedian, and Jrges Luis
> > > Borges
> > > Side question
> > >
> > > On Wed, Dec 1, 2021 at 1:30 PM Gary Kjos <garykjos at gmail.com> wrote:
> > >
> > > > Are you opening it from a shortcut or bookmark?
> > > >
> > > > Perhaps your shortcut or link is tied to a specific date.  Set the
> > > > link to a non-specific pointer
> > > >
> > > > https://calendar.google.com
> > > >
> > > >
> > > > On Wed, Dec 1, 2021 at 12:10 PM Arthur Fuller <fuller.artful at gmail.com
> > >
> > > > wrote:
> > > > >
> > > > > For some reason, Calendar always opens at October of this year. even
> > > if I
> > > > > jump to today, close it and re-open it, it opens at October. Any way
> > to
> > > > > make it open at Today?
> > > > >
> > > > > --
> > > > > Arthur
> > > > > --
> > > > > AccessD mailing list
> > > > > AccessD at databaseadvisors.com
> > > > > https://databaseadvisors.com/mailman/listinfo/accessd
> > > > > Website: http://www.databaseadvisors.com
> > > >
> > > >
> > > >
> > > > --
> > > > Gary Kjos
> > > > garykjos at gmail.com
> > > > --
> > > > AccessD mailing list
> > > > AccessD at databaseadvisors.com
> > > > https://databaseadvisors.com/mailman/listinfo/accessd
> > > > Website: http://www.databaseadvisors.com
> > > >
> > >
> > >
> > > --
> > > Arthur
> > > --
> > > 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
> >
>
>
> --
> Arthur
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com



-- 
Gary Kjos
garykjos at gmail.com

From fuller.artful at gmail.com  Wed Dec  1 18:44:24 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Wed, 1 Dec 2021 19:44:24 -0500
Subject: [AccessD] Small Google Calendar question
In-Reply-To: <CAJ2R_pJp+DeCnjUkkzisfhY4BRw+EnzxKJV26BjLLxk32H5JJw@mail.gmail.com>
References: <CAEPJO1hTOc5mx0x4nu2SYdLHx18+Mgm9szsbk2udrQx_7DbZjA@mail.gmail.com>
 <CAJ2R_p+KekNguU4Rm-tozUy3OONvFp-nKNvF74VueHa_qM4RCw@mail.gmail.com>
 <CAEPJO1j-UPSfx89tBSL4rN9TK-MbMS=oPO7rG56BtS9gqRmV2w@mail.gmail.com>
 <CAJLzs_2zrAweqnpwdCTYo+hDMibgD7cZ3KXGVGsL+MdksOZjSw@mail.gmail.com>
 <CAEPJO1g+WO6JH2zAHvXZVQnBTdZ6Fkg9AOD496R+ajrz1bxsPQ@mail.gmail.com>
 <CAJ2R_pJp+DeCnjUkkzisfhY4BRw+EnzxKJV26BjLLxk32H5JJw@mail.gmail.com>
Message-ID: <CAEPJO1gO_7LvT4F4paE6EgUGnSMabQizZnE1whmi0Daddn8qTA@mail.gmail.com>

Juice!
I like that the best of all submitted pronunciations. Yo, Juice!

On Wed, Dec 1, 2021 at 6:11 PM Gary Kjos <garykjos at gmail.com> wrote:

> RE: Pronouncing Kjos.
>
> I spell my name a lot.  Pretty much every time I need to give it.
> Probably at least twice most times.
>
> My family pronounces it with a CH sound.  Like the "Ch" in Chair at
> the beginning and like the "ose" in close on the back.  So Chose is an
> approximation. Throughout my school days I told people it was a silent
> K.  So just Jose
>
> My brother's buddies all call him Ka-Jose with two syllables.
>
> When I was introduced to some friends of friends for a golfing outing,
> the newly met people called me Juice.
>
> Thanks for asking.
>
> On Wed, Dec 1, 2021 at 2:13 PM Arthur Fuller <fuller.artful at gmail.com>
> wrote:
> >
> > I am going to guess "kiosk" but without the K, almost like Chaos.
> >
> > On Wed, Dec 1, 2021 at 2:45 PM Bill Benson <bensonforums at gmail.com>
> wrote:
> >
> > > how to pronounce [Gary's] surname
> > >
> > > Can we have a competition?
> > >
> > > On Wed, Dec 1, 2021 at 2:41 PM Arthur Fuller <fuller.artful at gmail.com>
> > > wrote:
> > >
> > > > Thanks, Gary, I'll give that a try. Side question. I have
> occasionally
> > > > puzzled over how to pronounce your surname.  My best guess is
> kee-yoss,
> > > but
> > > > that's as good as it gets, guess-wise. Another puzzle is the
> > > pronunciation
> > > > of Borge's given name. When I see his signature, I two things come
> > > > immediately to mind: Victore Borge, the pianist/comedian, and Jrges
> Luis
> > > > Borges
> > > > Side question
> > > >
> > > > On Wed, Dec 1, 2021 at 1:30 PM Gary Kjos <garykjos at gmail.com> wrote:
> > > >
> > > > > Are you opening it from a shortcut or bookmark?
> > > > >
> > > > > Perhaps your shortcut or link is tied to a specific date.  Set the
> > > > > link to a non-specific pointer
> > > > >
> > > > > https://calendar.google.com
> > > > >
> > > > >
> > > > > On Wed, Dec 1, 2021 at 12:10 PM Arthur Fuller <
> fuller.artful at gmail.com
> > > >
> > > > > wrote:
> > > > > >
> > > > > > For some reason, Calendar always opens at October of this year.
> even
> > > > if I
> > > > > > jump to today, close it and re-open it, it opens at October. Any
> way
> > > to
> > > > > > make it open at Today?
> > > > > >
> > > > > > --
> > > > > > Arthur
> > > > > > --
> > > > > > AccessD mailing list
> > > > > > AccessD at databaseadvisors.com
> > > > > > https://databaseadvisors.com/mailman/listinfo/accessd
> > > > > > Website: http://www.databaseadvisors.com
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Gary Kjos
> > > > > garykjos at gmail.com
> > > > > --
> > > > > AccessD mailing list
> > > > > AccessD at databaseadvisors.com
> > > > > https://databaseadvisors.com/mailman/listinfo/accessd
> > > > > Website: http://www.databaseadvisors.com
> > > > >
> > > >
> > > >
> > > > --
> > > > Arthur
> > > > --
> > > > 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
> > >
> >
> >
> > --
> > Arthur
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
>
>
>
> --
> Gary Kjos
> garykjos at gmail.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
Arthur

From fuller.artful at gmail.com  Mon Dec  6 19:26:15 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Mon, 6 Dec 2021 20:26:15 -0500
Subject: [AccessD] The most expensive desktop computer
Message-ID: <CAEPJO1jrDfP3i6hR2Aegrc6ubHN6vGVka3k8vtWxFHv7A8MtRg@mail.gmail.com>

Only $49K and change. Cheap at twice the price
<https://www.quora.com/What-is-the-most-expensive-desktop-PC-in-the-world-and-what-are-the-specs>
.

-- 
Arthur

From rockysmolin2 at gmail.com  Mon Dec  6 19:36:43 2021
From: rockysmolin2 at gmail.com (Rocky Smolin)
Date: Mon, 6 Dec 2021 17:36:43 -0800
Subject: [AccessD] The most expensive desktop computer
In-Reply-To: <CAEPJO1jrDfP3i6hR2Aegrc6ubHN6vGVka3k8vtWxFHv7A8MtRg@mail.gmail.com>
References: <CAEPJO1jrDfP3i6hR2Aegrc6ubHN6vGVka3k8vtWxFHv7A8MtRg@mail.gmail.com>
Message-ID: <CAEcmsdCoR_kNr+jsAYXKhFBtesb=MXBSD87cax1j6XUgb_ucew@mail.gmail.com>

This may be the link you meant to poast?  It answers the question:

The World's Most Expensive & Luxurious Gaming PC of 2021 (vizaca.com)
<https://www.vizaca.com/most-expensive-gaming-pc/>

r

On Mon, Dec 6, 2021 at 5:26 PM Arthur Fuller <fuller.artful at gmail.com>
wrote:

> Only $49K and change. Cheap at twice the price
> <
> https://www.quora.com/What-is-the-most-expensive-desktop-PC-in-the-world-and-what-are-the-specs
> >
> .
>
> --
> Arthur
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From garykjos at gmail.com  Mon Dec  6 19:44:43 2021
From: garykjos at gmail.com (Gary Kjos)
Date: Mon, 6 Dec 2021 19:44:43 -0600
Subject: [AccessD] The most expensive desktop computer
In-Reply-To: <CAEcmsdCoR_kNr+jsAYXKhFBtesb=MXBSD87cax1j6XUgb_ucew@mail.gmail.com>
References: <CAEPJO1jrDfP3i6hR2Aegrc6ubHN6vGVka3k8vtWxFHv7A8MtRg@mail.gmail.com>
 <CAEcmsdCoR_kNr+jsAYXKhFBtesb=MXBSD87cax1j6XUgb_ucew@mail.gmail.com>
Message-ID: <CAJ2R_p+dkSFWX9matsU=5_BfJdL=dQ5jt9xmbL2EAcVa-zw+7A@mail.gmail.com>

A reminder to all, this is the ACCESS LIST.

GK

On Mon, Dec 6, 2021 at 7:37 PM Rocky Smolin <rockysmolin2 at gmail.com> wrote:
>
> This may be the link you meant to poast?  It answers the question:
>
> The World's Most Expensive & Luxurious Gaming PC of 2021 (vizaca.com)
> <https://www.vizaca.com/most-expensive-gaming-pc/>
>
> r
>
> On Mon, Dec 6, 2021 at 5:26 PM Arthur Fuller <fuller.artful at gmail.com>
> wrote:
>
> > Only $49K and change. Cheap at twice the price
> > <
> > https://www.quora.com/What-is-the-most-expensive-desktop-PC-in-the-world-and-what-are-the-specs
> > >
> > .
> >
> > --
> > Arthur
> > --
> > 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



-- 
Gary Kjos
garykjos at gmail.com

From newsgrps at dalyn.co.nz  Tue Dec  7 18:09:26 2021
From: newsgrps at dalyn.co.nz (David Emerson)
Date: Wed, 8 Dec 2021 13:09:26 +1300
Subject: [AccessD] Changing DSN Connection strings
Message-ID: <005201d7ebc7$df552f00$9dff8d00$@dalyn.co.nz>

Hi Listers,

I have inherited a data base which has code which updates the connection
string of the tables between two different databases.  The user selects
which database to link to and the code updates the table's connect property:

tdf.Connect = strConnect_NEW

strConnect_NEW is in this format (with the actual password in place of
{Pwrd}):

ODBC:DSN= StockListSQL_Data_Archive;Description=
StockListSQL_Data_Archive;APP=Microsoft
Office;DATABASE=SL_DataSQL;User_Id=SQL_User;Password={Pwrd]

The only difference between the two connection strings in the name of the
Database

The Database could initially be connected to either of the SQL databases.
The first time the database connection is changed with this code:

                    tdf.Connect = strConnect_NEW
                    'Refresh the table link.
                    tdf.RefreshLink                     'Refresh the Link.

an SQL Server Login dialog box opens showing the Data Source, and Login ID,
and asking for the password.  Once the Password is entered then the user can
switch between the database tables without having to reenter the password.
However, if the Access program is closed and reopened then the first time
the database connection is changed the password is requested again.

Why is the Access program asking for the password when the password is
entered in the Connection string?  Is there some other connection that needs
the password saved in it?

When the DSN is set up for each user the "Connect to SQL Server to obtain
default settings for the additional configuration options" box is ticked and
the Login ID and Password is entered.

Regards

David Emerson
Dalyn Software Ltd
Wellington, New Zealand





From Paul.W at industrialcontrol.co.nz  Tue Dec  7 18:28:08 2021
From: Paul.W at industrialcontrol.co.nz (Paul Wolstenholme)
Date: Wed, 8 Dec 2021 13:28:08 +1300
Subject: [AccessD] Changing DSN Connection strings
In-Reply-To: <005201d7ebc7$df552f00$9dff8d00$@dalyn.co.nz>
References: <005201d7ebc7$df552f00$9dff8d00$@dalyn.co.nz>
Message-ID: <CABGHdVms7E0uS1zSH32nQoMATt=pTe9aiVSTUpbhS8z97wkGgw@mail.gmail.com>

David

You need to add this VBA line:
tdf.Attributes = tdf.Attributes Or dbAttachSavePWD

That corresponds to the linked table manager's pop-up that warns about
saving the password  with the linked table in the Access database file
because it isn't safe.  Some would suggest you should unlink all tables on
closing the database and relink them on opening (presumably they also
assume the front end is never shared).

Paul Wolstenholme

On Wed, 8 Dec 2021 at 13:10, David Emerson <newsgrps at dalyn.co.nz> wrote:

> Hi Listers,
>
> I have inherited a data base which has code which updates the connection
> string of the tables between two different databases.  The user selects
> which database to link to and the code updates the table's connect
> property:
>
> tdf.Connect = strConnect_NEW
>
> strConnect_NEW is in this format (with the actual password in place of
> {Pwrd}):
>
> ODBC:DSN= StockListSQL_Data_Archive;Description=
> StockListSQL_Data_Archive;APP=Microsoft
> Office;DATABASE=SL_DataSQL;User_Id=SQL_User;Password={Pwrd]
>
> The only difference between the two connection strings in the name of the
> Database
>
> The Database could initially be connected to either of the SQL databases.
> The first time the database connection is changed with this code:
>
>                     tdf.Connect = strConnect_NEW
>                     'Refresh the table link.
>                     tdf.RefreshLink                     'Refresh the Link.
>
> an SQL Server Login dialog box opens showing the Data Source, and Login ID,
> and asking for the password.  Once the Password is entered then the user
> can
> switch between the database tables without having to reenter the password.
> However, if the Access program is closed and reopened then the first time
> the database connection is changed the password is requested again.
>
> Why is the Access program asking for the password when the password is
> entered in the Connection string?  Is there some other connection that
> needs
> the password saved in it?
>
> When the DSN is set up for each user the "Connect to SQL Server to obtain
> default settings for the additional configuration options" box is ticked
> and
> the Login ID and Password is entered.
>
> Regards
>
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand
>
>
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From newsgrps at dalyn.co.nz  Tue Dec  7 18:42:24 2021
From: newsgrps at dalyn.co.nz (David Emerson)
Date: Wed, 8 Dec 2021 13:42:24 +1300
Subject: [AccessD] Changing DSN Connection strings
In-Reply-To: <CABGHdVms7E0uS1zSH32nQoMATt=pTe9aiVSTUpbhS8z97wkGgw@mail.gmail.com>
References: <005201d7ebc7$df552f00$9dff8d00$@dalyn.co.nz>
 <CABGHdVms7E0uS1zSH32nQoMATt=pTe9aiVSTUpbhS8z97wkGgw@mail.gmail.com>
Message-ID: <005d01d7ebcc$7a0fcab0$6e2f6010$@dalyn.co.nz>

Thanks Paul,

 

Should that be just before 

                    tdf.RefreshLink                     'Refresh the Link.



Regards

 

David

 

 

 

From: Paul Wolstenholme <Paul.W at industrialcontrol.co.nz> 
Sent: Wednesday, 8 December 2021 1:28 pm
To: newsgrps at dalyn.co.nz
Cc: AccessD <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Changing DSN Connection strings

 

David

 

You need to add this VBA line:

tdf.Attributes = tdf.Attributes Or dbAttachSavePWD


 

That corresponds to the linked table manager's pop-up that warns about saving the password  with the linked table in the Access database file because it isn't safe.  Some would suggest you should unlink all tables on closing the database and relink them on opening (presumably they also assume the front end is never shared).

 

Paul Wolstenholme

 

On Wed, 8 Dec 2021 at 13:10, David Emerson <newsgrps at dalyn.co.nz <mailto:newsgrps at dalyn.co.nz> > wrote:

Hi Listers,

I have inherited a data base which has code which updates the connection
string of the tables between two different databases.  The user selects
which database to link to and the code updates the table's connect property:

tdf.Connect = strConnect_NEW

strConnect_NEW is in this format (with the actual password in place of
{Pwrd}):

ODBC:DSN= StockListSQL_Data_Archive;Description=
StockListSQL_Data_Archive;APP=Microsoft
Office;DATABASE=SL_DataSQL;User_Id=SQL_User;Password={Pwrd]

The only difference between the two connection strings in the name of the
Database

The Database could initially be connected to either of the SQL databases.
The first time the database connection is changed with this code:

                    tdf.Connect = strConnect_NEW
                    'Refresh the table link.
                    tdf.RefreshLink                     'Refresh the Link.

an SQL Server Login dialog box opens showing the Data Source, and Login ID,
and asking for the password.  Once the Password is entered then the user can
switch between the database tables without having to reenter the password.
However, if the Access program is closed and reopened then the first time
the database connection is changed the password is requested again.

Why is the Access program asking for the password when the password is
entered in the Connection string?  Is there some other connection that needs
the password saved in it?

When the DSN is set up for each user the "Connect to SQL Server to obtain
default settings for the additional configuration options" box is ticked and
the Login ID and Password is entered.

Regards

David Emerson
Dalyn Software Ltd
Wellington, New Zealand




From newsgrps at dalyn.co.nz  Tue Dec  7 18:52:43 2021
From: newsgrps at dalyn.co.nz (David Emerson)
Date: Wed, 8 Dec 2021 13:52:43 +1300
Subject: [AccessD] Changing DSN Connection strings
In-Reply-To: <005d01d7ebcc$7a0fcab0$6e2f6010$@dalyn.co.nz>
References: <005201d7ebc7$df552f00$9dff8d00$@dalyn.co.nz>
 <CABGHdVms7E0uS1zSH32nQoMATt=pTe9aiVSTUpbhS8z97wkGgw@mail.gmail.com>
 <005d01d7ebcc$7a0fcab0$6e2f6010$@dalyn.co.nz>
Message-ID: <006201d7ebcd$eb1fc5b0$c15f5110$@dalyn.co.nz>

I tried that but got an Invalid Argument error.

-----Original Message-----
From: AccessD <accessd-bounces+newsgrps=dalyn.co.nz at databaseadvisors.com> On
Behalf Of David Emerson
Sent: Wednesday, 8 December 2021 1:42 pm
To: 'Paul Wolstenholme' <Paul.W at industrialcontrol.co.nz>
Cc: 'AccessD' <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Changing DSN Connection strings

Thanks Paul,

Should that be just before 
                    tdf.RefreshLink                     'Refresh the Link.

Regards
David

 

From: Paul Wolstenholme <Paul.W at industrialcontrol.co.nz>
Sent: Wednesday, 8 December 2021 1:28 pm
To: newsgrps at dalyn.co.nz
Cc: AccessD <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Changing DSN Connection strings

 David

You need to add this VBA line:
tdf.Attributes = tdf.Attributes Or dbAttachSavePWD

That corresponds to the linked table manager's pop-up that warns about
saving the password  with the linked table in the Access database file
because it isn't safe.  Some would suggest you should unlink all tables on
closing the database and relink them on opening (presumably they also assume
the front end is never shared).
 
Paul Wolstenholme
 

On Wed, 8 Dec 2021 at 13:10, David Emerson <newsgrps at dalyn.co.nz
<mailto:newsgrps at dalyn.co.nz> > wrote:

Hi Listers,

I have inherited a data base which has code which updates the connection
string of the tables between two different databases.  The user selects
which database to link to and the code updates the table's connect property:

tdf.Connect = strConnect_NEW

strConnect_NEW is in this format (with the actual password in place of
{Pwrd}):

ODBC:DSN= StockListSQL_Data_Archive;Description=
StockListSQL_Data_Archive;APP=Microsoft
Office;DATABASE=SL_DataSQL;User_Id=SQL_User;Password={Pwrd]

The only difference between the two connection strings in the name of the
Database

The Database could initially be connected to either of the SQL databases.
The first time the database connection is changed with this code:

                    tdf.Connect = strConnect_NEW
                    'Refresh the table link.
                    tdf.RefreshLink                     'Refresh the Link.

an SQL Server Login dialog box opens showing the Data Source, and Login ID,
and asking for the password.  Once the Password is entered then the user can
switch between the database tables without having to reenter the password.
However, if the Access program is closed and reopened then the first time
the database connection is changed the password is requested again.

Why is the Access program asking for the password when the password is
entered in the Connection string?  Is there some other connection that needs
the password saved in it?

When the DSN is set up for each user the "Connect to SQL Server to obtain
default settings for the additional configuration options" box is ticked and
the Login ID and Password is entered.

Regards

David Emerson
Dalyn Software Ltd
Wellington, New Zealand


From Paul.W at industrialcontrol.co.nz  Tue Dec  7 19:00:10 2021
From: Paul.W at industrialcontrol.co.nz (Paul Wolstenholme)
Date: Wed, 8 Dec 2021 14:00:10 +1300
Subject: [AccessD] Changing DSN Connection strings
In-Reply-To: <006201d7ebcd$eb1fc5b0$c15f5110$@dalyn.co.nz>
References: <005201d7ebc7$df552f00$9dff8d00$@dalyn.co.nz>
 <CABGHdVms7E0uS1zSH32nQoMATt=pTe9aiVSTUpbhS8z97wkGgw@mail.gmail.com>
 <005d01d7ebcc$7a0fcab0$6e2f6010$@dalyn.co.nz>
 <006201d7ebcd$eb1fc5b0$c15f5110$@dalyn.co.nz>
Message-ID: <CABGHdVno2m-ThbKQ_t3Zvk0dkX9_56UgFjhMpbXe7_pwBNJrDw@mail.gmail.com>

David,

This routine works for me in Access 2010 with SQL Server 2014:

===
Public Function LinkTableDAO( _
    ByRef stAccessTableName As String _
    , Optional ByRef stSourceTableName As String = "" _
    , Optional ByRef stConnectionString As String = "" _
    , Optional ByRef stDescription As String = "" _
    , Optional ByRef stIndexSQL As String = "" _
    , Optional ByRef bSavePassword As Boolean = False _
    ) As Boolean
' Based on:
'   Chipman & Baron pg 189
' Modified to accept connect string and support indexing (of views)
' Created ICEL.prw 10/11/2017.

    ' Un-links, Links or Re-links a single table(or view).
    ' Returns True on success.
On Error GoTo MyErrorHandler
    Dim db As DAO.Database
    Dim tdf As DAO.TableDef
    Dim prp As DAO.Property

    LinkTableDAO = False    ' default
    Set db = CurrentDb
    ' if the link already exists, delete it
On Error GoTo MyErrorHandlerNoLink
    Set tdf = db.TableDefs(stAccessTableName)
    ' Found an existing tabledef.
    If (tdf.Attributes And dbAttachedODBC) _
              <> dbAttachedODBC Then
        ' This isn't an ODBC linked table - ERROR
        Call LogError(-421001, "Table already exists but it is not an ODBC
link", "mICELBackEnd - LinkTableDAO()", stAccessTableName)
        GoTo MyExit
    End If
    db.TableDefs.Delete stAccessTableName
    db.TableDefs.Refresh
NoLinkExists:
On Error GoTo MyErrorHandler
    ' Interpret no connection string as do not link
    If "" = stConnectionString Then
        LinkTableDAO = True ' completed ok
        GoTo MyExit
    End If
    ' Create a new TableDef object
    Set tdf = db.CreateTableDef(stAccessTableName)
    ' Set the Connect and SourceTableName
    ' properties to establish the link
    tdf.Connect = stConnectionString
    tdf.SourceTableName = stSourceTableName
    If bSavePassword Then
        tdf.Attributes = tdf.Attributes Or dbAttachSavePWD
    End If
    ' Append to the database's TableDefs collection
    db.TableDefs.Append tdf
    ' Where it existed, add the Description property to the new table.
    If Len(stDescription) > 0 Then
      Set prp = tdf.CreateProperty("Description", dbText, stDescription)
      tdf.Properties.Append prp
    End If
    ' Create the index if specified
    If Len(stIndexSQL) > 0 Then
        CurrentDb.Execute stIndexSQL, dbFailOnError
    End If
    ' Turn off SubDataSheets
    ' tdf.Properties("SubDataSheetName").Value
    Set prp = tdf.CreateProperty("SubDataSheetName", dbText, "[None]")
    tdf.Properties.Append prp

    LinkTableDAO = True
MyExit:                 ' Label to resume after error.
On Error Resume Next
    Set prp = Nothing
    Set tdf = Nothing
    Exit Function       ' Exit before error handler.
MyErrorHandlerNoLink:   ' Handler for table not currently linked
    If 3265 = Err.Number Then Resume NoLinkExists   ' item not found in
this collection
MyErrorHandler:         ' Label to jump to on error.
    Call LogError(Err.Number, Err.Description, "mICELBackEnd -
LinkTableDAO()")
    LinkTableDAO = False
    Resume MyExit       ' Pick up again and quit.
    Resume              ' for debug (Set Next Statement)
End Function
===

Paul Wolstenholme


On Wed, 8 Dec 2021 at 13:53, David Emerson <newsgrps at dalyn.co.nz> wrote:

> I tried that but got an Invalid Argument error.
>
> -----Original Message-----
> From: AccessD <accessd-bounces+newsgrps=dalyn.co.nz at databaseadvisors.com>
> On
> Behalf Of David Emerson
> Sent: Wednesday, 8 December 2021 1:42 pm
> To: 'Paul Wolstenholme' <Paul.W at industrialcontrol.co.nz>
> Cc: 'AccessD' <accessd at databaseadvisors.com>
> Subject: Re: [AccessD] Changing DSN Connection strings
>
> Thanks Paul,
>
> Should that be just before
>                     tdf.RefreshLink                     'Refresh the Link.
>
> Regards
> David
>
>
>
> From: Paul Wolstenholme <Paul.W at industrialcontrol.co.nz>
> Sent: Wednesday, 8 December 2021 1:28 pm
> To: newsgrps at dalyn.co.nz
> Cc: AccessD <accessd at databaseadvisors.com>
> Subject: Re: [AccessD] Changing DSN Connection strings
>
>  David
>
> You need to add this VBA line:
> tdf.Attributes = tdf.Attributes Or dbAttachSavePWD
>
> That corresponds to the linked table manager's pop-up that warns about
> saving the password  with the linked table in the Access database file
> because it isn't safe.  Some would suggest you should unlink all tables on
> closing the database and relink them on opening (presumably they also
> assume
> the front end is never shared).
>
> Paul Wolstenholme
>
>
> On Wed, 8 Dec 2021 at 13:10, David Emerson <newsgrps at dalyn.co.nz
> <mailto:newsgrps at dalyn.co.nz> > wrote:
>
> Hi Listers,
>
> I have inherited a data base which has code which updates the connection
> string of the tables between two different databases.  The user selects
> which database to link to and the code updates the table's connect
> property:
>
> tdf.Connect = strConnect_NEW
>
> strConnect_NEW is in this format (with the actual password in place of
> {Pwrd}):
>
> ODBC:DSN= StockListSQL_Data_Archive;Description=
> StockListSQL_Data_Archive;APP=Microsoft
> Office;DATABASE=SL_DataSQL;User_Id=SQL_User;Password={Pwrd]
>
> The only difference between the two connection strings in the name of the
> Database
>
> The Database could initially be connected to either of the SQL databases.
> The first time the database connection is changed with this code:
>
>                     tdf.Connect = strConnect_NEW
>                     'Refresh the table link.
>                     tdf.RefreshLink                     'Refresh the Link.
>
> an SQL Server Login dialog box opens showing the Data Source, and Login ID,
> and asking for the password.  Once the Password is entered then the user
> can
> switch between the database tables without having to reenter the password.
> However, if the Access program is closed and reopened then the first time
> the database connection is changed the password is requested again.
>
> Why is the Access program asking for the password when the password is
> entered in the Connection string?  Is there some other connection that
> needs
> the password saved in it?
>
> When the DSN is set up for each user the "Connect to SQL Server to obtain
> default settings for the additional configuration options" box is ticked
> and
> the Login ID and Password is entered.
>
> Regards
>
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From newsgrps at dalyn.co.nz  Tue Dec  7 19:47:53 2021
From: newsgrps at dalyn.co.nz (David Emerson)
Date: Wed, 8 Dec 2021 14:47:53 +1300
Subject: [AccessD] Changing DSN Connection strings
In-Reply-To: <CABGHdVno2m-ThbKQ_t3Zvk0dkX9_56UgFjhMpbXe7_pwBNJrDw@mail.gmail.com>
References: <005201d7ebc7$df552f00$9dff8d00$@dalyn.co.nz>
 <CABGHdVms7E0uS1zSH32nQoMATt=pTe9aiVSTUpbhS8z97wkGgw@mail.gmail.com>
 <005d01d7ebcc$7a0fcab0$6e2f6010$@dalyn.co.nz>
 <006201d7ebcd$eb1fc5b0$c15f5110$@dalyn.co.nz>
 <CABGHdVno2m-ThbKQ_t3Zvk0dkX9_56UgFjhMpbXe7_pwBNJrDw@mail.gmail.com>
Message-ID: <006701d7ebd5$9f7279c0$de576d40$@dalyn.co.nz>

Ah, that is for creating a table link.  I was hoping for something easier
but may need to go down the delete and recreate link path.

-----Original Message-----
From: AccessD <accessd-bounces+newsgrps=dalyn.co.nz at databaseadvisors.com> On
Behalf Of Paul Wolstenholme
Sent: Wednesday, 8 December 2021 2:00 pm
To: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>; David Emerson <David at dalyn.co.nz>
Subject: Re: [AccessD] Changing DSN Connection strings

David,

This routine works for me in Access 2010 with SQL Server 2014:

===
Public Function LinkTableDAO( _
    ByRef stAccessTableName As String _
    , Optional ByRef stSourceTableName As String = "" _
    , Optional ByRef stConnectionString As String = "" _
    , Optional ByRef stDescription As String = "" _
    , Optional ByRef stIndexSQL As String = "" _
    , Optional ByRef bSavePassword As Boolean = False _
    ) As Boolean
' Based on:
'   Chipman & Baron pg 189
' Modified to accept connect string and support indexing (of views) '
Created ICEL.prw 10/11/2017.

    ' Un-links, Links or Re-links a single table(or view).
    ' Returns True on success.
On Error GoTo MyErrorHandler
    Dim db As DAO.Database
    Dim tdf As DAO.TableDef
    Dim prp As DAO.Property

    LinkTableDAO = False    ' default
    Set db = CurrentDb
    ' if the link already exists, delete it On Error GoTo
MyErrorHandlerNoLink
    Set tdf = db.TableDefs(stAccessTableName)
    ' Found an existing tabledef.
    If (tdf.Attributes And dbAttachedODBC) _
              <> dbAttachedODBC Then
        ' This isn't an ODBC linked table - ERROR
        Call LogError(-421001, "Table already exists but it is not an ODBC
link", "mICELBackEnd - LinkTableDAO()", stAccessTableName)
        GoTo MyExit
    End If
    db.TableDefs.Delete stAccessTableName
    db.TableDefs.Refresh
NoLinkExists:
On Error GoTo MyErrorHandler
    ' Interpret no connection string as do not link
    If "" = stConnectionString Then
        LinkTableDAO = True ' completed ok
        GoTo MyExit
    End If
    ' Create a new TableDef object
    Set tdf = db.CreateTableDef(stAccessTableName)
    ' Set the Connect and SourceTableName
    ' properties to establish the link
    tdf.Connect = stConnectionString
    tdf.SourceTableName = stSourceTableName
    If bSavePassword Then
        tdf.Attributes = tdf.Attributes Or dbAttachSavePWD
    End If
    ' Append to the database's TableDefs collection
    db.TableDefs.Append tdf
    ' Where it existed, add the Description property to the new table.
    If Len(stDescription) > 0 Then
      Set prp = tdf.CreateProperty("Description", dbText, stDescription)
      tdf.Properties.Append prp
    End If
    ' Create the index if specified
    If Len(stIndexSQL) > 0 Then
        CurrentDb.Execute stIndexSQL, dbFailOnError
    End If
    ' Turn off SubDataSheets
    ' tdf.Properties("SubDataSheetName").Value
    Set prp = tdf.CreateProperty("SubDataSheetName", dbText, "[None]")
    tdf.Properties.Append prp

    LinkTableDAO = True
MyExit:                 ' Label to resume after error.
On Error Resume Next
    Set prp = Nothing
    Set tdf = Nothing
    Exit Function       ' Exit before error handler.
MyErrorHandlerNoLink:   ' Handler for table not currently linked
    If 3265 = Err.Number Then Resume NoLinkExists   ' item not found in
this collection
MyErrorHandler:         ' Label to jump to on error.
    Call LogError(Err.Number, Err.Description, "mICELBackEnd -
LinkTableDAO()")
    LinkTableDAO = False
    Resume MyExit       ' Pick up again and quit.
    Resume              ' for debug (Set Next Statement)
End Function
===

Paul Wolstenholme


On Wed, 8 Dec 2021 at 13:53, David Emerson <newsgrps at dalyn.co.nz> wrote:

> I tried that but got an Invalid Argument error.
>
> -----Original Message-----
> From: AccessD 
> <accessd-bounces+newsgrps=dalyn.co.nz at databaseadvisors.com>
> On
> Behalf Of David Emerson
> Sent: Wednesday, 8 December 2021 1:42 pm
> To: 'Paul Wolstenholme' <Paul.W at industrialcontrol.co.nz>
> Cc: 'AccessD' <accessd at databaseadvisors.com>
> Subject: Re: [AccessD] Changing DSN Connection strings
>
> Thanks Paul,
>
> Should that be just before
>                     tdf.RefreshLink                     'Refresh the Link.
>
> Regards
> David
>
>
>
> From: Paul Wolstenholme <Paul.W at industrialcontrol.co.nz>
> Sent: Wednesday, 8 December 2021 1:28 pm
> To: newsgrps at dalyn.co.nz
> Cc: AccessD <accessd at databaseadvisors.com>
> Subject: Re: [AccessD] Changing DSN Connection strings
>
>  David
>
> You need to add this VBA line:
> tdf.Attributes = tdf.Attributes Or dbAttachSavePWD
>
> That corresponds to the linked table manager's pop-up that warns about 
> saving the password  with the linked table in the Access database file 
> because it isn't safe.  Some would suggest you should unlink all 
> tables on closing the database and relink them on opening (presumably 
> they also assume the front end is never shared).
>
> Paul Wolstenholme
>
>
> On Wed, 8 Dec 2021 at 13:10, David Emerson <newsgrps at dalyn.co.nz 
> <mailto:newsgrps at dalyn.co.nz> > wrote:
>
> Hi Listers,
>
> I have inherited a data base which has code which updates the 
> connection string of the tables between two different databases.  The 
> user selects which database to link to and the code updates the 
> table's connect
> property:
>
> tdf.Connect = strConnect_NEW
>
> strConnect_NEW is in this format (with the actual password in place of
> {Pwrd}):
>
> ODBC:DSN= StockListSQL_Data_Archive;Description=
> StockListSQL_Data_Archive;APP=Microsoft
> Office;DATABASE=SL_DataSQL;User_Id=SQL_User;Password={Pwrd]
>
> The only difference between the two connection strings in the name of 
> the Database
>
> The Database could initially be connected to either of the SQL databases.
> The first time the database connection is changed with this code:
>
>                     tdf.Connect = strConnect_NEW
>                     'Refresh the table link.
>                     tdf.RefreshLink                     'Refresh the Link.
>
> an SQL Server Login dialog box opens showing the Data Source, and 
> Login ID, and asking for the password.  Once the Password is entered 
> then the user can switch between the database tables without having to 
> reenter the password.
> However, if the Access program is closed and reopened then the first 
> time the database connection is changed the password is requested again.
>
> Why is the Access program asking for the password when the password is 
> entered in the Connection string?  Is there some other connection that 
> needs the password saved in it?
>
> When the DSN is set up for each user the "Connect to SQL Server to 
> obtain default settings for the additional configuration options" box 
> is ticked and the Login ID and Password is entered.
>
> Regards
>
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand


From gustav at cactus.dk  Wed Dec  8 01:25:35 2021
From: gustav at cactus.dk (Gustav Brock)
Date: Wed, 8 Dec 2021 07:25:35 +0000
Subject: [AccessD] Changing DSN Connection strings
Message-ID: <AS8PR10MB4360BE4633BB06C7A4C02257CA6F9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>

Hi David

We use DSN-less connections, which I've found are easier to control:

<code>
' Top level call example:
IsAttached = AttachSqlServer(Me!Hostname.Value, Me!Database.Value, Me!Username.Value, Me!Password.Value)


Public Function AttachSqlServer( _
    ByVal Hostname As String, _
    ByVal Database As String, _
    ByVal Username As String, _
    ByVal Password As String) _
    As Boolean

' Attach all tables linked via ODBC to SQL Server or Azure SQL.
' 2016-04-24. Cactus Data ApS, CPH.

    Const cstrDbType    As String = "ODBC"
    Const cstrAcPrefix  As String = "dbo_"

    Dim dbs             As DAO.Database
    Dim tdf             As DAO.TableDef
    Dim qdf             As DAO.QueryDef
    
    Dim strConnect      As String
    Dim strName         As String
    
    On Error GoTo Err_AttachSqlServer
    
    Set dbs = CurrentDb
    strConnect = ConnectionString(Hostname, Database, Username, Password)
    
    For Each tdf In dbs.TableDefs
        strName = tdf.Name
        If Asc(strName) <> Asc("~") Then
            If InStr(tdf.Connect, cstrDbType) = 1 Then
                If Left(strName, Len(cstrAcPrefix)) = cstrAcPrefix Then
                    tdf.Name = Mid(strName, Len(cstrAcPrefix) + 1)
                End If
                tdf.Connect = strConnect
                tdf.RefreshLink
                Debug.Print Timer, tdf.Name, tdf.SourceTableName, tdf.Connect
                DoEvents
            End If
        End If
    Next
    
    For Each qdf In dbs.QueryDefs
        If qdf.Connect <> "" Then
            Debug.Print Timer, qdf.Name, qdf.Type, qdf.Connect
            qdf.Connect = strConnect
        End If
    Next
    Debug.Print "Done!"
    
    AttachSqlServer = True
    
Exit_AttachSqlServer:
    Set tdf = Nothing
    Set dbs = Nothing
    Exit Function
    
Err_AttachSqlServer:
    Call ErrorMox
    Resume Exit_AttachSqlServer
    
End Function


Public Function ConnectionString( _
    ByVal Hostname As String, _
    ByVal Database As String, _
    ByVal Username As String, _
    ByVal Password As String, _
    Optional ByVal AdoStyle As Boolean) _
    As String

' Create ODBC or ADO connection string from its variable elements.
' 2021-06-15. Cactus Data ApS, CPH.

    Const AzureDomain   As String = ".windows.net"
    Const OdbcPrefix    As String = "ODBC;"
    Const OdbcConnect   As String = _
        "DRIVER=SQL Server Native Client 17.0;" & _
        "Description=Your Application Name;" & _
        "APP=Microsoft? Access;" & _
        "SERVER={0};" & _
        "DATABASE={1};" & _
        "UID={2};" & _
        "PWD={3};" & _
        "Trusted_Connection={4};"
        
    Dim FullConnect     As String
    
    If Right(Hostname, Len(AzureDomain)) = AzureDomain Then
        ' Azure SQL connection.
        ' Append servername to username.
        Username = Username & "@" & Split(Hostname)(0)
    End If
    If Not AdoStyle Then
        FullConnect = OdbcPrefix
    End If
    FullConnect = FullConnect & OdbcConnect
    FullConnect = Replace(FullConnect, "{0}", Hostname)
    FullConnect = Replace(FullConnect, "{1}", Database)
    FullConnect = Replace(FullConnect, "{2}", Username)
    FullConnect = Replace(FullConnect, "{3}", Password)
    FullConnect = Replace(FullConnect, "{4}", IIf(Username & Password = "", "Yes", "No"))
    
    ConnectionString = FullConnect

End Function
</code>

-----Oprindelig meddelelse-----
Fra: AccessD <accessd-bounces+gustav=cactus.dk at databaseadvisors.com> P? vegne af David Emerson
Sendt: 8. december 2021 01:09
Til: AccessD <accessd at databaseadvisors.com>
Emne: [AccessD] Changing DSN Connection strings

Hi Listers,

I have inherited a data base which has code which updates the connection string of the tables between two different databases.  The user selects which database to link to and the code updates the table's connect property:

tdf.Connect = strConnect_NEW

strConnect_NEW is in this format (with the actual password in place of
{Pwrd}):

ODBC:DSN= StockListSQL_Data_Archive;Description=
StockListSQL_Data_Archive;APP=Microsoft
Office;DATABASE=SL_DataSQL;User_Id=SQL_User;Password={Pwrd]

The only difference between the two connection strings in the name of the Database

<snip>
The Database could initially be connected to either of the SQL databases.
The first time the database connection is changed with this code:

                    tdf.Connect = strConnect_NEW
                    'Refresh the table link.
                    tdf.RefreshLink                     'Refresh the Link.

an SQL Server Login dialog box opens showing the Data Source, and Login ID, and asking for the password.  Once the Password is entered then the user can switch between the database tables without having to reenter the password.
However, if the Access program is closed and reopened then the first time the database connection is changed the password is requested again.

Why is the Access program asking for the password when the password is entered in the Connection string?  Is there some other connection that needs the password saved in it?

When the DSN is set up for each user the "Connect to SQL Server to obtain default settings for the additional configuration options" box is ticked and the Login ID and Password is entered.

Regards

David Emerson
Dalyn Software Ltd
Wellington, New Zealand 

From stuart at lexacorp.com.pg  Wed Dec  8 02:26:23 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Wed, 08 Dec 2021 18:26:23 +1000
Subject: [AccessD] Changing DSN Connection strings
In-Reply-To: <AS8PR10MB4360BE4633BB06C7A4C02257CA6F9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
References: <AS8PR10MB4360BE4633BB06C7A4C02257CA6F9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
Message-ID: <61B06C2F.27295.203A697@stuart.lexacorp.com.pg>

Me too. I gave up messing with DSNs on user's computers years ago. It was always a PITA. 
.
Build the connection string(s) into a VBA module and you know it will always be correct.


On 8 Dec 2021 at 7:25, Gustav Brock via AccessD wrote:

> Hi David
> 
> We use DSN-less connections, which I've found are easier to control:
> 


From Paul.W at industrialcontrol.co.nz  Wed Dec  8 13:49:11 2021
From: Paul.W at industrialcontrol.co.nz (Paul Wolstenholme)
Date: Thu, 9 Dec 2021 08:49:11 +1300
Subject: [AccessD] Changing DSN Connection strings
In-Reply-To: <61B06C2F.27295.203A697@stuart.lexacorp.com.pg>
References: <AS8PR10MB4360BE4633BB06C7A4C02257CA6F9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
 <61B06C2F.27295.203A697@stuart.lexacorp.com.pg>
Message-ID: <CABGHdV=9jxTTm4EQPcGKj4SnX=T2Vepe2vjnaHMvkv=SXHT4yw@mail.gmail.com>

I also endorse the use of DSNless connection strings (except maybe when you
first inherit an existing project).  The answer I supplied (detailing the
saving of the password in the front end) is applicable to both DSNless
connection strings and connection strings that use DSNs.

Paul Wolstenholme


On Wed, 8 Dec 2021 at 21:26, Stuart McLachlan <stuart at lexacorp.com.pg>
wrote:

> Me too. I gave up messing with DSNs on user's computers years ago. It was
> always a PITA.
> .
> Build the connection string(s) into a VBA module and you know it will
> always be correct.
>
>
> On 8 Dec 2021 at 7:25, Gustav Brock via AccessD wrote:
>
> > Hi David
> >
> > We use DSN-less connections, which I've found are easier to control:
> >
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From newsgrps at dalyn.co.nz  Wed Dec  8 14:09:38 2021
From: newsgrps at dalyn.co.nz (David Emerson)
Date: Thu, 9 Dec 2021 09:09:38 +1300
Subject: [AccessD] Changing DSN Connection strings
In-Reply-To: <CABGHdV=9jxTTm4EQPcGKj4SnX=T2Vepe2vjnaHMvkv=SXHT4yw@mail.gmail.com>
References: <AS8PR10MB4360BE4633BB06C7A4C02257CA6F9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
 <61B06C2F.27295.203A697@stuart.lexacorp.com.pg>
 <CABGHdV=9jxTTm4EQPcGKj4SnX=T2Vepe2vjnaHMvkv=SXHT4yw@mail.gmail.com>
Message-ID: <001001d7ec6f$8949f750$9bdde5f0$@dalyn.co.nz>

Thanks Everyone.  I came to the same conclusion.  None of my own
applications have ever used DSN connections.  This is a project that I have
just inherited, and I am working through their list of problems.  Most of
them relate to the connection method.  I will be converting it to DNS-Less
connection.

Regards

David



-----Original Message-----
From: AccessD <accessd-bounces+newsgrps=dalyn.co.nz at databaseadvisors.com> On
Behalf Of Paul Wolstenholme
Sent: Thursday, 9 December 2021 8:49 am
To: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] Changing DSN Connection strings

I also endorse the use of DSNless connection strings (except maybe when you
first inherit an existing project).  The answer I supplied (detailing the
saving of the password in the front end) is applicable to both DSNless
connection strings and connection strings that use DSNs.

Paul Wolstenholme


On Wed, 8 Dec 2021 at 21:26, Stuart McLachlan <stuart at lexacorp.com.pg>
wrote:

> Me too. I gave up messing with DSNs on user's computers years ago. It 
> was always a PITA.
> .
> Build the connection string(s) into a VBA module and you know it will 
> always be correct.
>
>
> On 8 Dec 2021 at 7:25, Gustav Brock via AccessD wrote:
>
> > Hi David
> >
> > We use DSN-less connections, which I've found are easier to control:


From anita at ddisolutions.com.au  Mon Dec 13 17:13:27 2021
From: anita at ddisolutions.com.au (Anita Smith)
Date: Mon, 13 Dec 2021 23:13:27 +0000
Subject: [AccessD] Timestamp in merge database
Message-ID: <SYBP282MB0475A6DFA9A959C4876439D3FF749@SYBP282MB0475.AUSP282.PROD.OUTLOOK.COM>

I have a database that I am converting from Access ADP to ODBC.

I am coming across some issues with editing of records causing write conflicts in the tables with only one user editing records. I have changed all my bit fields to default and not allowing nulls as this can cause this problem.

I am not having much luck - however adding a timestamp field to the tables fixes the problem perfectly. I am now in the dilemma that I don't want to add this field to my replicated table in the fear of buggering up the synchronisation (I don't want to ruin my Christmas).

Is there anyone out there with any experience regarding adding timestamp fields in replicated databases? I will note that the table in question is only replicated one way - i.e. the subscribers don't edit the records.

Anita



From pcs.accessd at gmail.com  Mon Dec 13 17:51:50 2021
From: pcs.accessd at gmail.com (Borge Hansen)
Date: Tue, 14 Dec 2021 09:51:50 +1000
Subject: [AccessD] Timestamp in merge database
In-Reply-To: <SYBP282MB0475A6DFA9A959C4876439D3FF749@SYBP282MB0475.AUSP282.PROD.OUTLOOK.COM>
References: <SYBP282MB0475A6DFA9A959C4876439D3FF749@SYBP282MB0475.AUSP282.PROD.OUTLOOK.COM>
Message-ID: <CAF+SPM9GB3mrAkBPnPvUMm76_VKPeNrSOWDmZ3ksvEKXBdUCsQ@mail.gmail.com>

This article may give you some tips

https://www.mssqltips.com/sqlservertip/4545/synchronizing-sql-server-data-using-rowversion/

/borge

On Tue, 14 Dec 2021 at 9:13 am, Anita Smith <anita at ddisolutions.com.au>
wrote:

> I have a database that I am converting from Access ADP to ODBC.
>
> I am coming across some issues with editing of records causing write
> conflicts in the tables with only one user editing records. I have changed
> all my bit fields to default and not allowing nulls as this can cause this
> problem.
>
> I am not having much luck - however adding a timestamp field to the tables
> fixes the problem perfectly. I am now in the dilemma that I don't want to
> add this field to my replicated table in the fear of buggering up the
> synchronisation (I don't want to ruin my Christmas).
>
> Is there anyone out there with any experience regarding adding timestamp
> fields in replicated databases? I will note that the table in question is
> only replicated one way - i.e. the subscribers don't edit the records.
>
> Anita
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From anita at ddisolutions.com.au  Mon Dec 13 18:07:24 2021
From: anita at ddisolutions.com.au (Anita Smith)
Date: Tue, 14 Dec 2021 00:07:24 +0000
Subject: [AccessD] Timestamp in merge database
In-Reply-To: <CAF+SPM9GB3mrAkBPnPvUMm76_VKPeNrSOWDmZ3ksvEKXBdUCsQ@mail.gmail.com>
References: <SYBP282MB0475A6DFA9A959C4876439D3FF749@SYBP282MB0475.AUSP282.PROD.OUTLOOK.COM>
 <CAF+SPM9GB3mrAkBPnPvUMm76_VKPeNrSOWDmZ3ksvEKXBdUCsQ@mail.gmail.com>
Message-ID: <SYBP282MB047528A95E86031D67D69A3BFF759@SYBP282MB0475.AUSP282.PROD.OUTLOOK.COM>

Thanks Borge - or is that B?rge - your name sounds Danish.

Very nice explanation of the timestamp field. Unfortunately it did not cover adding a timestamp field after the replication has commenced.  I'm thinking I will add the field just before the Christmas shutdown and face the consequences.

Anita


-----Original Message-----
From: AccessD <accessd-bounces+anita=ddisolutions.com.au at databaseadvisors.com> On Behalf Of Borge Hansen
Sent: Tuesday, 14 December 2021 10:52
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Timestamp in merge database

This article may give you some tips

https://www.mssqltips.com/sqlservertip/4545/synchronizing-sql-server-data-using-rowversion/

/borge

On Tue, 14 Dec 2021 at 9:13 am, Anita Smith <anita at ddisolutions.com.au>
wrote:

> I have a database that I am converting from Access ADP to ODBC.
>
> I am coming across some issues with editing of records causing write 
> conflicts in the tables with only one user editing records. I have 
> changed all my bit fields to default and not allowing nulls as this 
> can cause this problem.
>
> I am not having much luck - however adding a timestamp field to the 
> tables fixes the problem perfectly. I am now in the dilemma that I 
> don't want to add this field to my replicated table in the fear of 
> buggering up the synchronisation (I don't want to ruin my Christmas).
>
> Is there anyone out there with any experience regarding adding 
> timestamp fields in replicated databases? I will note that the table 
> in question is only replicated one way - i.e. the subscribers don't edit the records.
>
> Anita
>
>
> --
> 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

From pcs.accessd at gmail.com  Mon Dec 13 19:15:05 2021
From: pcs.accessd at gmail.com (Borge Hansen)
Date: Tue, 14 Dec 2021 11:15:05 +1000
Subject: [AccessD] Timestamp in merge database
In-Reply-To: <SYBP282MB047528A95E86031D67D69A3BFF759@SYBP282MB0475.AUSP282.PROD.OUTLOOK.COM>
References: <SYBP282MB0475A6DFA9A959C4876439D3FF749@SYBP282MB0475.AUSP282.PROD.OUTLOOK.COM>
 <CAF+SPM9GB3mrAkBPnPvUMm76_VKPeNrSOWDmZ3ksvEKXBdUCsQ@mail.gmail.com>
 <SYBP282MB047528A95E86031D67D69A3BFF759@SYBP282MB0475.AUSP282.PROD.OUTLOOK.COM>
Message-ID: <CAF+SPM_KrKHpY72d6kjvb+xTuQfb5ehQKd3QC67bwz1RvK7xfw@mail.gmail.com>

Anita,
Yes it?s B?rge - but who can pronounce that except for a few million Danes.
Perhaps you can create a test environment and simply test it out - it may
save your festive season :)

On Tue, 14 Dec 2021 at 10:07 am, Anita Smith <anita at ddisolutions.com.au>
wrote:

> Thanks Borge - or is that B?rge - your name sounds Danish.
>
> Very nice explanation of the timestamp field. Unfortunately it did not
> cover adding a timestamp field after the replication has commenced.  I'm
> thinking I will add the field just before the Christmas shutdown and face
> the consequences.
>
> Anita
>
>
> -----Original Message-----
> From: AccessD <accessd-bounces+anita=
> ddisolutions.com.au at databaseadvisors.com> On Behalf Of Borge Hansen
> Sent: Tuesday, 14 December 2021 10:52
> To: Access Developers discussion and problem solving <
> accessd at databaseadvisors.com>
> Subject: Re: [AccessD] Timestamp in merge database
>
> This article may give you some tips
>
>
> https://www.mssqltips.com/sqlservertip/4545/synchronizing-sql-server-data-using-rowversion/
>
> /borge
>
> On Tue, 14 Dec 2021 at 9:13 am, Anita Smith <anita at ddisolutions.com.au>
> wrote:
>
> > I have a database that I am converting from Access ADP to ODBC.
> >
> > I am coming across some issues with editing of records causing write
> > conflicts in the tables with only one user editing records. I have
> > changed all my bit fields to default and not allowing nulls as this
> > can cause this problem.
> >
> > I am not having much luck - however adding a timestamp field to the
> > tables fixes the problem perfectly. I am now in the dilemma that I
> > don't want to add this field to my replicated table in the fear of
> > buggering up the synchronisation (I don't want to ruin my Christmas).
> >
> > Is there anyone out there with any experience regarding adding
> > timestamp fields in replicated databases? I will note that the table
> > in question is only replicated one way - i.e. the subscribers don't edit
> the records.
> >
> > Anita
> >
> >
> > --
> > 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
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From stuart at lexacorp.com.pg  Mon Dec 13 19:27:52 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Tue, 14 Dec 2021 11:27:52 +1000
Subject: [AccessD] Timestamp in merge database
In-Reply-To: <CAF+SPM_KrKHpY72d6kjvb+xTuQfb5ehQKd3QC67bwz1RvK7xfw@mail.gmail.com>
References: <SYBP282MB0475A6DFA9A959C4876439D3FF749@SYBP282MB0475.AUSP282.PROD.OUTLOOK.COM>,
 <SYBP282MB047528A95E86031D67D69A3BFF759@SYBP282MB0475.AUSP282.PROD.OUTLOOK.COM>,
 <CAF+SPM_KrKHpY72d6kjvb+xTuQfb5ehQKd3QC67bwz1RvK7xfw@mail.gmail.com>
Message-ID: <61B7F318.9153.860DE5D@stuart.lexacorp.com.pg>

I find it hard to believe that it sounds anything like this: L) 
https://forvo.com/word/b%C3%B8rge/

On 14 Dec 2021 at 11:15, Borge Hansen wrote:

> Anita,
> Yes it?s B?rge - but who can pronounce that except for a few
> million Danes. 

From anita at ddisolutions.com.au  Mon Dec 13 19:32:32 2021
From: anita at ddisolutions.com.au (Anita Smith)
Date: Tue, 14 Dec 2021 01:32:32 +0000
Subject: [AccessD] Timestamp in merge database
In-Reply-To: <61B7F318.9153.860DE5D@stuart.lexacorp.com.pg>
References: <SYBP282MB0475A6DFA9A959C4876439D3FF749@SYBP282MB0475.AUSP282.PROD.OUTLOOK.COM>,
 <SYBP282MB047528A95E86031D67D69A3BFF759@SYBP282MB0475.AUSP282.PROD.OUTLOOK.COM>,
 <CAF+SPM_KrKHpY72d6kjvb+xTuQfb5ehQKd3QC67bwz1RvK7xfw@mail.gmail.com>
 <61B7F318.9153.860DE5D@stuart.lexacorp.com.pg>
Message-ID: <SYBP282MB0475FA548A0398F1903E33E8FF759@SYBP282MB0475.AUSP282.PROD.OUTLOOK.COM>

As a Dane I can verify that that pronunciation is spot on.

Danish it not for the faint of heart.

Anita


-----Original Message-----
From: AccessD <accessd-bounces+anita=ddisolutions.com.au at databaseadvisors.com> On Behalf Of Stuart McLachlan
Sent: Tuesday, 14 December 2021 12:28
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Timestamp in merge database

I find it hard to believe that it sounds anything like this: L) https://forvo.com/word/b%C3%B8rge/

On 14 Dec 2021 at 11:15, Borge Hansen wrote:

> Anita,
> Yes it?s B?rge - but who can pronounce that except for a few million 
> Danes.
--
AccessD mailing list
AccessD at databaseadvisors.com
https://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

From gustav at cactus.dk  Tue Dec 14 02:33:22 2021
From: gustav at cactus.dk (Gustav Brock)
Date: Tue, 14 Dec 2021 08:33:22 +0000
Subject: [AccessD] Timestamp in merge database
Message-ID: <AS8PR10MB436016A0EED906765A5BE7A3CA759@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>

Hi Stuart

Why is that so hard? 
Anita is right; it is spot on.

/gustav

-----Oprindelig meddelelse-----
Fra: AccessD <accessd-bounces+gustav=cactus.dk at databaseadvisors.com> P? vegne af Anita Smith
Sendt: 14. december 2021 02:33
Til: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Emne: Re: [AccessD] Timestamp in merge database

As a Dane I can verify that that pronunciation is spot on.

Danish it not for the faint of heart.

Anita


-----Original Message-----
From: AccessD <accessd-bounces+anita=ddisolutions.com.au at databaseadvisors.com> On Behalf Of Stuart McLachlan
Sent: Tuesday, 14 December 2021 12:28
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Timestamp in merge database

I find it hard to believe that it sounds anything like this: L) https://forvo.com/word/b%C3%B8rge/

On 14 Dec 2021 at 11:15, Borge Hansen wrote:

> Anita,
> Yes it?s B?rge - but who can pronounce that except for a few million 
> Danes. 

From gustav at cactus.dk  Tue Dec 14 02:39:44 2021
From: gustav at cactus.dk (Gustav Brock)
Date: Tue, 14 Dec 2021 08:39:44 +0000
Subject: [AccessD] Timestamp in merge database
Message-ID: <AS8PR10MB43601A0008CADD21CD9F8C0CCA759@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>

Hi Anita

I thought it was the other way round: That a timestamp/rowversion is mandatory for replication.

But I haven't used replication with SQL Server.

/gustav

-----Oprindelig meddelelse-----

> On Tue, 14 Dec 2021 at 9:13 am, Anita Smith <anita at ddisolutions.com.au>
> wrote:
>
> > I have a database that I am converting from Access ADP to ODBC.
> >
> > I am coming across some issues with editing of records causing write 
> > conflicts in the tables with only one user editing records. I have 
> > changed all my bit fields to default and not allowing nulls as this 
> > can cause this problem.
> >
> > I am not having much luck - however adding a timestamp field to the 
> > tables fixes the problem perfectly. I am now in the dilemma that I 
> > don't want to add this field to my replicated table in the fear of 
> > buggering up the synchronisation (I don't want to ruin my Christmas).
> >
> > Is there anyone out there with any experience regarding adding 
> > timestamp fields in replicated databases? I will note that the table 
> > in question is only replicated one way - i.e. the subscribers don't edit
> > the records.
> >
> > Anita 

From anita at ddisolutions.com.au  Tue Dec 14 03:01:05 2021
From: anita at ddisolutions.com.au (Anita Smith)
Date: Tue, 14 Dec 2021 09:01:05 +0000
Subject: [AccessD] Timestamp in merge database
In-Reply-To: <AS8PR10MB43601A0008CADD21CD9F8C0CCA759@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
References: <AS8PR10MB43601A0008CADD21CD9F8C0CCA759@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
Message-ID: <SYBP282MB04756C6E33D746E5AFB7A5E5FF759@SYBP282MB0475.AUSP282.PROD.OUTLOOK.COM>

It sort of is  if you start off that way. I'm 20 years in on this one.

Gosh - I'm getting old.

I'm going to take the risk and add the field over the weekend and announce my retirement on Monday morning .... maybe.

Anita



-------- Original message --------
From: Gustav Brock via AccessD <accessd at databaseadvisors.com>
Date: 14/12/21 7:39 pm (GMT+10:00)
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Cc: Gustav Brock <gustav at cactus.dk>
Subject: Re: [AccessD] Timestamp in merge database

Hi Anita

I thought it was the other way round: That a timestamp/rowversion is mandatory for replication.

But I haven't used replication with SQL Server.

/gustav

-----Oprindelig meddelelse-----

> On Tue, 14 Dec 2021 at 9:13 am, Anita Smith <anita at ddisolutions.com.au>
> wrote:
>
> > I have a database that I am converting from Access ADP to ODBC.
> >
> > I am coming across some issues with editing of records causing write
> > conflicts in the tables with only one user editing records. I have
> > changed all my bit fields to default and not allowing nulls as this
> > can cause this problem.
> >
> > I am not having much luck - however adding a timestamp field to the
> > tables fixes the problem perfectly. I am now in the dilemma that I
> > don't want to add this field to my replicated table in the fear of
> > buggering up the synchronisation (I don't want to ruin my Christmas).
> >
> > Is there anyone out there with any experience regarding adding
> > timestamp fields in replicated databases? I will note that the table
> > in question is only replicated one way - i.e. the subscribers don't edit
> > the records.
> >
> > Anita
--
AccessD mailing list
AccessD at databaseadvisors.com
https://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

From fuller.artful at gmail.com  Sun Dec 19 12:30:59 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Sun, 19 Dec 2021 13:30:59 -0500
Subject: [AccessD] Alias Question
Message-ID: <CAEPJO1i+Ds8xBtPdvCLDZ_OR=ZnbrfOrkKigzWFZMtZ6ZrsCng@mail.gmail.com>

Given a function declaration such as this(from ADH, by Getz et. al.):
<code>
Declare Function WM_apiGetDesktopWindow _
Lib "user32" Alias "GetDesktopWindow" () As Long
</code>

What purpose does the Alias serve?

-- 
Arthur

From charlotte.foust at gmail.com  Sun Dec 19 13:34:48 2021
From: charlotte.foust at gmail.com (Charlotte Foust)
Date: Sun, 19 Dec 2021 11:34:48 -0800
Subject: [AccessD] Alias Question
In-Reply-To: <CAEPJO1i+Ds8xBtPdvCLDZ_OR=ZnbrfOrkKigzWFZMtZ6ZrsCng@mail.gmail.com>
References: <CAEPJO1i+Ds8xBtPdvCLDZ_OR=ZnbrfOrkKigzWFZMtZ6ZrsCng@mail.gmail.com>
Message-ID: <CAH+Met8yfz8ujQLgN5JpXX-fA380cc_q+=fd_Zi8qPEgJZDXQw@mail.gmail.com>

You use the alias to call the function.

Charlotte Foust
(916) 206-4336


On Sun, Dec 19, 2021 at 10:31 AM Arthur Fuller <fuller.artful at gmail.com>
wrote:

> Given a function declaration such as this(from ADH, by Getz et. al.):
> <code>
> Declare Function WM_apiGetDesktopWindow _
> Lib "user32" Alias "GetDesktopWindow" () As Long
> </code>
>
> What purpose does the Alias serve?
>
> --
> Arthur
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From stuart at lexacorp.com.pg  Sun Dec 19 14:46:18 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Mon, 20 Dec 2021 06:46:18 +1000
Subject: [AccessD] Alias Question
In-Reply-To: <CAEPJO1i+Ds8xBtPdvCLDZ_OR=ZnbrfOrkKigzWFZMtZ6ZrsCng@mail.gmail.com>
References: <CAEPJO1i+Ds8xBtPdvCLDZ_OR=ZnbrfOrkKigzWFZMtZ6ZrsCng@mail.gmail.com>
Message-ID: <61BF9A1A.24074.1A53DF88@stuart.lexacorp.com.pg>

It is the exact name of the function as the it appears in the  DLL. You can declare the 
function with any function name you want in your code, but you must give the correct actual 
name, with correct capitalisation, as it appears in the function as the ALIAS because that is 
how your code finds it in the DLL.

In your example, the actual exported function n the DLL is called GetDesktopWindow (not 
captialization).

You could call get the Desktop WIndow handle with hWNd = GetWinNAme() if you declared 
your function like this:
Declare Function myGetWInName _
Lib "user32" Alias "GetDesktopWindow" () As Long

If you did this (note incorrect capitalization), calling your function would give an error since 
their is no such function in the DLL.
Declare Function WM_apiGetDesktopWindow _
Lib "user32" Alias "Getdesktopwindow" () As Long



On 19 Dec 2021 at 13:30, Arthur Fuller wrote:

> Given a function declaration such as this(from ADH, by Getz et. al.):
> <code> Declare Function WM_apiGetDesktopWindow _ Lib "user32" Alias
> "GetDesktopWindow" () As Long </code>
> 
> What purpose does the Alias serve?
> 
> -- 
> Arthur
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 



From stuart at lexacorp.com.pg  Sun Dec 19 14:46:18 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Mon, 20 Dec 2021 06:46:18 +1000
Subject: [AccessD] Alias Question
In-Reply-To: <CAH+Met8yfz8ujQLgN5JpXX-fA380cc_q+=fd_Zi8qPEgJZDXQw@mail.gmail.com>
References: <CAEPJO1i+Ds8xBtPdvCLDZ_OR=ZnbrfOrkKigzWFZMtZ6ZrsCng@mail.gmail.com>,
 <CAH+Met8yfz8ujQLgN5JpXX-fA380cc_q+=fd_Zi8qPEgJZDXQw@mail.gmail.com>
Message-ID: <61BF9A1A.9394.1A53E024@stuart.lexacorp.com.pg>

VBA uses the ALIAS to locate the function. YOU use the name you declare.

On 19 Dec 2021 at 11:34, Charlotte Foust wrote:

> You use the alias to call the function.
> 
> Charlotte Foust
> (916) 206-4336
> 
> 
> On Sun, Dec 19, 2021 at 10:31 AM Arthur Fuller
> <fuller.artful at gmail.com> wrote:
> 
> > Given a function declaration such as this(from ADH, by Getz et.
> > al.): <code> Declare Function WM_apiGetDesktopWindow _ Lib "user32"
> > Alias "GetDesktopWindow" () As Long </code>
> >
> > What purpose does the Alias serve?
> >
> > --
> > Arthur
> > --
> > 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
> 



From stuart at lexacorp.com.pg  Sun Dec 19 14:52:55 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Mon, 20 Dec 2021 06:52:55 +1000
Subject: [AccessD] Alias Question
In-Reply-To: <61BF9A1A.24074.1A53DF88@stuart.lexacorp.com.pg>
References: <CAEPJO1i+Ds8xBtPdvCLDZ_OR=ZnbrfOrkKigzWFZMtZ6ZrsCng@mail.gmail.com>,
 <61BF9A1A.24074.1A53DF88@stuart.lexacorp.com.pg>
Message-ID: <61BF9BA7.2605.1A59ED85@stuart.lexacorp.com.pg>

Doh - too early in the morning, lots of typos :(

GetWInName/myGetWinName
n/in
not/note cpitalisation
their/there


On 20 Dec 2021 at 6:46, Stuart McLachlan wrote:

> It is the exact name of the function as the it appears in the  DLL.
> You can declare the function with any function name you want in your
> code, but you must give the correct actual name, with correct
> capitalisation, as it appears in the function as the ALIAS because
> that is how your code finds it in the DLL.
> 
> In your example, the actual exported function n the DLL is called
> GetDesktopWindow (not captialization).
> 
> You could call get the Desktop WIndow handle with hWNd = GetWinNAme()
> if you declared your function like this: Declare Function myGetWInName
> _ Lib "user32" Alias "GetDesktopWindow" () As Long
> 
> If you did this (note incorrect capitalization), calling your function
> would give an error since their is no such function in the DLL.
> Declare Function WM_apiGetDesktopWindow _ Lib "user32" Alias
> "Getdesktopwindow" () As Long
> 
> 
> 
> On 19 Dec 2021 at 13:30, Arthur Fuller wrote:
> 
> > Given a function declaration such as this(from ADH, by Getz et.
> > al.): <code> Declare Function WM_apiGetDesktopWindow _ Lib "user32"
> > Alias "GetDesktopWindow" () As Long </code>
> > 
> > What purpose does the Alias serve?
> > 
> > -- 
> > Arthur
> > -- 
> > 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
> 



From fuller.artful at gmail.com  Sun Dec 19 15:24:38 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Sun, 19 Dec 2021 16:24:38 -0500
Subject: [AccessD] Alias Question
In-Reply-To: <CAH+Met8yfz8ujQLgN5JpXX-fA380cc_q+=fd_Zi8qPEgJZDXQw@mail.gmail.com>
References: <CAEPJO1i+Ds8xBtPdvCLDZ_OR=ZnbrfOrkKigzWFZMtZ6ZrsCng@mail.gmail.com>
 <CAH+Met8yfz8ujQLgN5JpXX-fA380cc_q+=fd_Zi8qPEgJZDXQw@mail.gmail.com>
Message-ID: <CAEPJO1j8bYLqwYpQvsdqqVYB1QG6OUtvsCwdpegKoLvLkV+1PQ@mail.gmail.com>

Charlotte,
I guessed that much.. Perhaps my question should have been Why? What's the
advantage of using an alias when you already have the function name?

On Sun, Dec 19, 2021 at 2:35 PM Charlotte Foust <charlotte.foust at gmail.com>
wrote:

> You use the alias to call the function.
>
> Charlotte Foust
> (916) 206-4336
>
>
> On Sun, Dec 19, 2021 at 10:31 AM Arthur Fuller <fuller.artful at gmail.com>
> wrote:
>
> > Given a function declaration such as this(from ADH, by Getz et. al.):
> > <code>
> > Declare Function WM_apiGetDesktopWindow _
> > Lib "user32" Alias "GetDesktopWindow" () As Long
> > </code>
> >
> > What purpose does the Alias serve?
> >
> > --
> > Arthur
> > --
> > 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
>


-- 
Arthur

From stuart at lexacorp.com.pg  Sun Dec 19 15:39:00 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Mon, 20 Dec 2021 07:39:00 +1000
Subject: [AccessD] Alias Question
In-Reply-To: <CAEPJO1j8bYLqwYpQvsdqqVYB1QG6OUtvsCwdpegKoLvLkV+1PQ@mail.gmail.com>
References: <CAEPJO1i+Ds8xBtPdvCLDZ_OR=ZnbrfOrkKigzWFZMtZ6ZrsCng@mail.gmail.com>,
 <CAH+Met8yfz8ujQLgN5JpXX-fA380cc_q+=fd_Zi8qPEgJZDXQw@mail.gmail.com>,
 <CAEPJO1j8bYLqwYpQvsdqqVYB1QG6OUtvsCwdpegKoLvLkV+1PQ@mail.gmail.com>
Message-ID: <61BFA674.29708.1A841E2D@stuart.lexacorp.com.pg>

You guessed wrong. Charlotte is mistaken. Se my longer response.  :)

On 19 Dec 2021 at 16:24, Arthur Fuller wrote:

> Charlotte,
> I guessed that much.. Perhaps my question should have been Why? What's
> the advantage of using an alias when you already have the function
> name?
> 
> On Sun, Dec 19, 2021 at 2:35 PM Charlotte Foust
> <charlotte.foust at gmail.com> wrote:
> 
> > You use the alias to call the function.
> >
> > Charlotte Foust
> > (916) 206-4336
> >
> >
> > On Sun, Dec 19, 2021 at 10:31 AM Arthur Fuller
> > <fuller.artful at gmail.com> wrote:
> >
> > > Given a function declaration such as this(from ADH, by Getz et.
> > > al.): <code> Declare Function WM_apiGetDesktopWindow _ Lib
> > > "user32" Alias "GetDesktopWindow" () As Long </code>
> > >
> > > What purpose does the Alias serve?
> > >
> > > --
> > > Arthur
> > > --
> > > 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
> >
> 
> 
> -- 
> Arthur
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 



From fuller.artful at gmail.com  Sun Dec 19 16:18:14 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Sun, 19 Dec 2021 17:18:14 -0500
Subject: [AccessD] Alias Question
In-Reply-To: <61BFA674.29708.1A841E2D@stuart.lexacorp.com.pg>
References: <CAEPJO1i+Ds8xBtPdvCLDZ_OR=ZnbrfOrkKigzWFZMtZ6ZrsCng@mail.gmail.com>
 <CAH+Met8yfz8ujQLgN5JpXX-fA380cc_q+=fd_Zi8qPEgJZDXQw@mail.gmail.com>
 <CAEPJO1j8bYLqwYpQvsdqqVYB1QG6OUtvsCwdpegKoLvLkV+1PQ@mail.gmail.com>
 <61BFA674.29708.1A841E2D@stuart.lexacorp.com.pg>
Message-ID: <CAEPJO1h3dzvTTy0hmoqxcakURKGh8fy81FicgMKz=G1kFSm3nQ@mail.gmail.com>

Stuart,
I look firward to your longer response. Where is it?

On Sun, Dec 19, 2021 at 4:39 PM Stuart McLachlan <stuart at lexacorp.com.pg>
wrote:

> You guessed wrong. Charlotte is mistaken. Se my longer response.  :)
>
> On 19 Dec 2021 at 16:24, Arthur Fuller wrote:
>
> > Charlotte,
> > I guessed that much.. Perhaps my question should have been Why? What's
> > the advantage of using an alias when you already have the function
> > name?
> >
> > On Sun, Dec 19, 2021 at 2:35 PM Charlotte Foust
> > <charlotte.foust at gmail.com> wrote:
> >
> > > You use the alias to call the function.
> > >
> > > Charlotte Foust
> > > (916) 206-4336
> > >
> > >
> > > On Sun, Dec 19, 2021 at 10:31 AM Arthur Fuller
> > > <fuller.artful at gmail.com> wrote:
> > >
> > > > Given a function declaration such as this(from ADH, by Getz et.
> > > > al.): <code> Declare Function WM_apiGetDesktopWindow _ Lib
> > > > "user32" Alias "GetDesktopWindow" () As Long </code>
> > > >
> > > > What purpose does the Alias serve?
> > > >
> > > > --
> > > > Arthur
> > > > --
> > > > 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
> > >
> >
> >
> > --
> > Arthur
> > --
> > 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
>


-- 
Arthur

From garykjos at gmail.com  Sun Dec 19 16:52:42 2021
From: garykjos at gmail.com (Gary Kjos)
Date: Sun, 19 Dec 2021 16:52:42 -0600
Subject: [AccessD] Alias Question
In-Reply-To: <61BF9A1A.24074.1A53DF88@stuart.lexacorp.com.pg>
References: <CAEPJO1i+Ds8xBtPdvCLDZ_OR=ZnbrfOrkKigzWFZMtZ6ZrsCng@mail.gmail.com>
 <61BF9A1A.24074.1A53DF88@stuart.lexacorp.com.pg>
Message-ID: <CAJ2R_pLnHVjJVvFxL_EUkB9-EV+ckBHxeP4xjxXzfji6u+JvzA@mail.gmail.com>

Here us Stuarts earlier long response Arthur.....

On Sun, Dec 19, 2021 at 2:46 PM Stuart McLachlan <stuart at lexacorp.com.pg> wrote:
>
> It is the exact name of the function as the it appears in the  DLL. You can declare the
> function with any function name you want in your code, but you must give the correct actual
> name, with correct capitalisation, as it appears in the function as the ALIAS because that is
> how your code finds it in the DLL.
>
> In your example, the actual exported function n the DLL is called GetDesktopWindow (not
> captialization).
>
> You could call get the Desktop WIndow handle with hWNd = GetWinNAme() if you declared
> your function like this:
> Declare Function myGetWInName _
> Lib "user32" Alias "GetDesktopWindow" () As Long
>
> If you did this (note incorrect capitalization), calling your function would give an error since
> their is no such function in the DLL.
> Declare Function WM_apiGetDesktopWindow _
> Lib "user32" Alias "Getdesktopwindow" () As Long
>
>
>
> On 19 Dec 2021 at 13:30, Arthur Fuller wrote:
>
> > Given a function declaration such as this(from ADH, by Getz et. al.):
> > <code> Declare Function WM_apiGetDesktopWindow _ Lib "user32" Alias
> > "GetDesktopWindow" () As Long </code>
> >
> > What purpose does the Alias serve?
> >
> > --
> > Arthur
> > --
> > 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



-- 
Gary Kjos
garykjos at gmail.com

From fuller.artful at gmail.com  Sun Dec 19 17:31:22 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Sun, 19 Dec 2021 18:31:22 -0500
Subject: [AccessD] Alias Question
In-Reply-To: <CAJ2R_pLnHVjJVvFxL_EUkB9-EV+ckBHxeP4xjxXzfji6u+JvzA@mail.gmail.com>
References: <CAEPJO1i+Ds8xBtPdvCLDZ_OR=ZnbrfOrkKigzWFZMtZ6ZrsCng@mail.gmail.com>
 <61BF9A1A.24074.1A53DF88@stuart.lexacorp.com.pg>
 <CAJ2R_pLnHVjJVvFxL_EUkB9-EV+ckBHxeP4xjxXzfji6u+JvzA@mail.gmail.com>
Message-ID: <CAEPJO1hC-SuD95xaL6RpFuKTX=HZbhu5KxAR9gp-4YTCmaqAog@mail.gmail.com>

Thanks Gary and Stuart. That clears things up.

On Sun, Dec 19, 2021 at 5:53 PM Gary Kjos <garykjos at gmail.com> wrote:

> Here us Stuarts earlier long response Arthur.....
>
> On Sun, Dec 19, 2021 at 2:46 PM Stuart McLachlan <stuart at lexacorp.com.pg>
> wrote:
> >
> > It is the exact name of the function as the it appears in the  DLL. You
> can declare the
> > function with any function name you want in your code, but you must give
> the correct actual
> > name, with correct capitalisation, as it appears in the function as the
> ALIAS because that is
> > how your code finds it in the DLL.
> >
> > In your example, the actual exported function n the DLL is called
> GetDesktopWindow (not
> > captialization).
> >
> > You could call get the Desktop WIndow handle with hWNd = GetWinNAme() if
> you declared
> > your function like this:
> > Declare Function myGetWInName _
> > Lib "user32" Alias "GetDesktopWindow" () As Long
> >
> > If you did this (note incorrect capitalization), calling your function
> would give an error since
> > their is no such function in the DLL.
> > Declare Function WM_apiGetDesktopWindow _
> > Lib "user32" Alias "Getdesktopwindow" () As Long
> >
> >
> >
> > On 19 Dec 2021 at 13:30, Arthur Fuller wrote:
> >
> > > Given a function declaration such as this(from ADH, by Getz et. al.):
> > > <code> Declare Function WM_apiGetDesktopWindow _ Lib "user32" Alias
> > > "GetDesktopWindow" () As Long </code>
> > >
> > > What purpose does the Alias serve?
> > >
> > > --
> > > Arthur
> > > --
> > > 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
>
>
>
> --
> Gary Kjos
> garykjos at gmail.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
Arthur

From jamesbutton at blueyonder.co.uk  Sun Dec 19 18:15:42 2021
From: jamesbutton at blueyonder.co.uk (James Button)
Date: Mon, 20 Dec 2021 00:15:42 -0000
Subject: [AccessD] Alias Question
In-Reply-To: <CAEPJO1hC-SuD95xaL6RpFuKTX=HZbhu5KxAR9gp-4YTCmaqAog@mail.gmail.com>
References: <CAEPJO1i+Ds8xBtPdvCLDZ_OR=ZnbrfOrkKigzWFZMtZ6ZrsCng@mail.gmail.com>
 <61BF9A1A.24074.1A53DF88@stuart.lexacorp.com.pg>
 <CAJ2R_pLnHVjJVvFxL_EUkB9-EV+ckBHxeP4xjxXzfji6u+JvzA@mail.gmail.com>
 <CAEPJO1hC-SuD95xaL6RpFuKTX=HZbhu5KxAR9gp-4YTCmaqAog@mail.gmail.com>
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAAO8VDlNCBfdEkctCy61lm0HCgAAAEAAAAGJMMtzYXohAvVFcgm5xdmkBAAAAAA==@blueyonder.co.uk>

Re the use of the Alias.

That  is something I have used to  create functional  processes that are
replacements for  supplied modules that didn't quite seem to do what was needed
-
As in it not checking the parameters for conformity  and not generate
appropriate error messages as in  it's nice to know what file is inaccessible
rather than have to figure it out from a generic 'can't be bothered'  error
code.

JimB

-----Original Message-----
From: AccessD
<accessd-bounces+jamesbutton=blueyonder.co.uk at databaseadvisors.com> On Behalf Of
Arthur Fuller
Sent: Sunday, December 19, 2021 11:31 PM
To: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] Alias Question

Thanks Gary and Stuart. That clears things up.

On Sun, Dec 19, 2021 at 5:53 PM Gary Kjos <garykjos at gmail.com> wrote:

> Here us Stuarts earlier long response Arthur.....
>
> On Sun, Dec 19, 2021 at 2:46 PM Stuart McLachlan <stuart at lexacorp.com.pg>
> wrote:
> >
> > It is the exact name of the function as the it appears in the  DLL. You
> can declare the
> > function with any function name you want in your code, but you must give
> the correct actual
> > name, with correct capitalisation, as it appears in the function as the
> ALIAS because that is
> > how your code finds it in the DLL.
> >
> > In your example, the actual exported function n the DLL is called
> GetDesktopWindow (not
> > captialization).
> >
> > You could call get the Desktop WIndow handle with hWNd = GetWinNAme() if
> you declared
> > your function like this:
> > Declare Function myGetWInName _
> > Lib "user32" Alias "GetDesktopWindow" () As Long
> >
> > If you did this (note incorrect capitalization), calling your function
> would give an error since
> > their is no such function in the DLL.
> > Declare Function WM_apiGetDesktopWindow _
> > Lib "user32" Alias "Getdesktopwindow" () As Long
> >
> >
> >
> > On 19 Dec 2021 at 13:30, Arthur Fuller wrote:
> >
> > > Given a function declaration such as this(from ADH, by Getz et. al.):
> > > <code> Declare Function WM_apiGetDesktopWindow _ Lib "user32" Alias
> > > "GetDesktopWindow" () As Long </code>
> > >
> > > What purpose does the Alias serve?
> > >
> > > --
> > > Arthur
> > > --
> > > 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
>
>
>
> --
> Gary Kjos
> garykjos at gmail.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


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


From stuart at lexacorp.com.pg  Sun Dec 19 18:36:37 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Mon, 20 Dec 2021 10:36:37 +1000
Subject: [AccessD] Alias Question
In-Reply-To: <CAEPJO1hC-SuD95xaL6RpFuKTX=HZbhu5KxAR9gp-4YTCmaqAog@mail.gmail.com>
References: <CAEPJO1i+Ds8xBtPdvCLDZ_OR=ZnbrfOrkKigzWFZMtZ6ZrsCng@mail.gmail.com>,
 <CAJ2R_pLnHVjJVvFxL_EUkB9-EV+ckBHxeP4xjxXzfji6u+JvzA@mail.gmail.com>,
 <CAEPJO1hC-SuD95xaL6RpFuKTX=HZbhu5KxAR9gp-4YTCmaqAog@mail.gmail.com>
Message-ID: <61BFD015.16232.1B26B912@stuart.lexacorp.com.pg>

It's also worth noting that in VBA, you don't need an ALIAS if you don't rename the function:

Declare Function GetDesktopWindow Lib "user32" () As Long
...
Debug.Print GetDesktopWindow
...

-- 
Stuart


On 19 Dec 2021 at 18:31, Arthur Fuller wrote:

> Thanks Gary and Stuart. That clears things up.
> 
> On Sun, Dec 19, 2021 at 5:53 PM Gary Kjos <garykjos at gmail.com> wrote:
> 
> > Here us Stuarts earlier long response Arthur.....
> >
> > On Sun, Dec 19, 2021 at 2:46 PM Stuart McLachlan
> > <stuart at lexacorp.com.pg> wrote:
> > >
> > > It is the exact name of the function as the it appears in the 
> > > DLL. You
> > can declare the
> > > function with any function name you want in your code, but you
> > > must give
> > the correct actual
> > > name, with correct capitalisation, as it appears in the function
> > > as the
> > ALIAS because that is
> > > how your code finds it in the DLL.
> > >
> > > In your example, the actual exported function n the DLL is called
> > GetDesktopWindow (not
> > > captialization).
> > >
> > > You could call get the Desktop WIndow handle with hWNd =
> > > GetWinNAme() if
> > you declared
> > > your function like this:
> > > Declare Function myGetWInName _
> > > Lib "user32" Alias "GetDesktopWindow" () As Long
> > >
> > > If you did this (note incorrect capitalization), calling your
> > > function
> > would give an error since
> > > their is no such function in the DLL.
> > > Declare Function WM_apiGetDesktopWindow _
> > > Lib "user32" Alias "Getdesktopwindow" () As Long
> > >
> > >
> > >
> > > On 19 Dec 2021 at 13:30, Arthur Fuller wrote:
> > >
> > > > Given a function declaration such as this(from ADH, by Getz et.
> > > > al.): <code> Declare Function WM_apiGetDesktopWindow _ Lib
> > > > "user32" Alias "GetDesktopWindow" () As Long </code>
> > > >
> > > > What purpose does the Alias serve?
> > > >
> > > > --
> > > > Arthur
> > > > --
> > > > 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
> >
> >
> >
> > --
> > Gary Kjos
> > garykjos at gmail.com
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
> 
> 
> -- 
> Arthur
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 



From fuller.artful at gmail.com  Sun Dec 19 21:04:32 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Sun, 19 Dec 2021 22:04:32 -0500
Subject: [AccessD] Alias Question
In-Reply-To: <61BFD015.16232.1B26B912@stuart.lexacorp.com.pg>
References: <CAEPJO1i+Ds8xBtPdvCLDZ_OR=ZnbrfOrkKigzWFZMtZ6ZrsCng@mail.gmail.com>
 <CAJ2R_pLnHVjJVvFxL_EUkB9-EV+ckBHxeP4xjxXzfji6u+JvzA@mail.gmail.com>
 <CAEPJO1hC-SuD95xaL6RpFuKTX=HZbhu5KxAR9gp-4YTCmaqAog@mail.gmail.com>
 <61BFD015.16232.1B26B912@stuart.lexacorp.com.pg>
Message-ID: <CAEPJO1hTsszrLbMX=rs9ztB3FfYYXK_W6sbxLPCpnacZjJoDrg@mail.gmail.com>

The past that I am not understanding is why I would want to rename a
function unless it had a really long name that was a hassle to type.

On Sun, Dec 19, 2021 at 7:37 PM Stuart McLachlan <stuart at lexacorp.com.pg>
wrote:

> It's also worth noting that in VBA, you don't need an ALIAS if you don't
> rename the function:
>
> Declare Function GetDesktopWindow Lib "user32" () As Long
> ...
> Debug.Print GetDesktopWindow
> ...
>
> --
> Stuart
>
>
> On 19 Dec 2021 at 18:31, Arthur Fuller wrote:
>
> > Thanks Gary and Stuart. That clears things up.
> >
> > On Sun, Dec 19, 2021 at 5:53 PM Gary Kjos <garykjos at gmail.com> wrote:
> >
> > > Here us Stuarts earlier long response Arthur.....
> > >
> > > On Sun, Dec 19, 2021 at 2:46 PM Stuart McLachlan
> > > <stuart at lexacorp.com.pg> wrote:
> > > >
> > > > It is the exact name of the function as the it appears in the
> > > > DLL. You
> > > can declare the
> > > > function with any function name you want in your code, but you
> > > > must give
> > > the correct actual
> > > > name, with correct capitalisation, as it appears in the function
> > > > as the
> > > ALIAS because that is
> > > > how your code finds it in the DLL.
> > > >
> > > > In your example, the actual exported function n the DLL is called
> > > GetDesktopWindow (not
> > > > captialization).
> > > >
> > > > You could call get the Desktop WIndow handle with hWNd =
> > > > GetWinNAme() if
> > > you declared
> > > > your function like this:
> > > > Declare Function myGetWInName _
> > > > Lib "user32" Alias "GetDesktopWindow" () As Long
> > > >
> > > > If you did this (note incorrect capitalization), calling your
> > > > function
> > > would give an error since
> > > > their is no such function in the DLL.
> > > > Declare Function WM_apiGetDesktopWindow _
> > > > Lib "user32" Alias "Getdesktopwindow" () As Long
> > > >
> > > >
> > > >
> > > > On 19 Dec 2021 at 13:30, Arthur Fuller wrote:
> > > >
> > > > > Given a function declaration such as this(from ADH, by Getz et.
> > > > > al.): <code> Declare Function WM_apiGetDesktopWindow _ Lib
> > > > > "user32" Alias "GetDesktopWindow" () As Long </code>
> > > > >
> > > > > What purpose does the Alias serve?
> > > > >
> > > > > --
> > > > > Arthur
> > > > > --
> > > > > 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
> > >
> > >
> > >
> > > --
> > > Gary Kjos
> > > garykjos at gmail.com
> > > --
> > > AccessD mailing list
> > > AccessD at databaseadvisors.com
> > > https://databaseadvisors.com/mailman/listinfo/accessd
> > > Website: http://www.databaseadvisors.com
> > >
> >
> >
> > --
> > Arthur
> > --
> > 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
>


-- 
Arthur

From stuart at lexacorp.com.pg  Sun Dec 19 21:53:56 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Mon, 20 Dec 2021 13:53:56 +1000
Subject: [AccessD] Alias Question
In-Reply-To: <CAEPJO1hTsszrLbMX=rs9ztB3FfYYXK_W6sbxLPCpnacZjJoDrg@mail.gmail.com>
References: <CAEPJO1i+Ds8xBtPdvCLDZ_OR=ZnbrfOrkKigzWFZMtZ6ZrsCng@mail.gmail.com>,
 <61BFD015.16232.1B26B912@stuart.lexacorp.com.pg>,
 <CAEPJO1hTsszrLbMX=rs9ztB3FfYYXK_W6sbxLPCpnacZjJoDrg@mail.gmail.com>
Message-ID: <61BFFE54.10861.1BDB5F39@stuart.lexacorp.com.pg>

Two possibilities:
1. If you want to abbreviate a long name, or 
2. If the original name of a function contains characters that are illegal in a 
function name in your development enviornment
e.g.:
DECLARE FUNCTION LegalName ALIAS "Illegal$Name" ...
DECLARE FUNCTION LegalName ALIAS "3IllegalName" ...
DECLARE FUNCTION LegalName ALIAS "_IllegalName" ...


On 19 Dec 2021 at 22:04, Arthur Fuller wrote:

> The past that I am not understanding is why I would want to rename a
> function unless it had a really long name that was a hassle to type.
> 
> On Sun, Dec 19, 2021 at 7:37 PM Stuart McLachlan
> <stuart at lexacorp.com.pg> wrote:
> 
> > It's also worth noting that in VBA, you don't need an ALIAS if you
> > don't rename the function:
> >
> > Declare Function GetDesktopWindow Lib "user32" () As Long
> > ...
> > Debug.Print GetDesktopWindow
> > ...
> >
> > --
> > Stuart
> >
> >
> > On 19 Dec 2021 at 18:31, Arthur Fuller wrote:
> >
> > > Thanks Gary and Stuart. That clears things up.
> > >
> > > On Sun, Dec 19, 2021 at 5:53 PM Gary Kjos <garykjos at gmail.com>
> > > wrote:
> > >
> > > > Here us Stuarts earlier long response Arthur.....
> > > >
> > > > On Sun, Dec 19, 2021 at 2:46 PM Stuart McLachlan
> > > > <stuart at lexacorp.com.pg> wrote:
> > > > >
> > > > > It is the exact name of the function as the it appears in the
> > > > > DLL. You
> > > > can declare the
> > > > > function with any function name you want in your code, but you
> > > > > must give
> > > > the correct actual
> > > > > name, with correct capitalisation, as it appears in the
> > > > > function as the
> > > > ALIAS because that is
> > > > > how your code finds it in the DLL.
> > > > >
> > > > > In your example, the actual exported function n the DLL is
> > > > > called
> > > > GetDesktopWindow (not
> > > > > captialization).
> > > > >
> > > > > You could call get the Desktop WIndow handle with hWNd =
> > > > > GetWinNAme() if
> > > > you declared
> > > > > your function like this:
> > > > > Declare Function myGetWInName _
> > > > > Lib "user32" Alias "GetDesktopWindow" () As Long
> > > > >
> > > > > If you did this (note incorrect capitalization), calling your
> > > > > function
> > > > would give an error since
> > > > > their is no such function in the DLL.
> > > > > Declare Function WM_apiGetDesktopWindow _
> > > > > Lib "user32" Alias "Getdesktopwindow" () As Long
> > > > >
> > > > >
> > > > >
> > > > > On 19 Dec 2021 at 13:30, Arthur Fuller wrote:
> > > > >
> > > > > > Given a function declaration such as this(from ADH, by Getz
> > > > > > et. al.): <code> Declare Function WM_apiGetDesktopWindow _
> > > > > > Lib "user32" Alias "GetDesktopWindow" () As Long </code>
> > > > > >
> > > > > > What purpose does the Alias serve?
> > > > > >
> > > > > > --
> > > > > > Arthur
> > > > > > --
> > > > > > 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
> > > >
> > > >
> > > >
> > > > --
> > > > Gary Kjos
> > > > garykjos at gmail.com
> > > > --
> > > > AccessD mailing list
> > > > AccessD at databaseadvisors.com
> > > > https://databaseadvisors.com/mailman/listinfo/accessd
> > > > Website: http://www.databaseadvisors.com
> > > >
> > >
> > >
> > > --
> > > Arthur
> > > --
> > > 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
> >
> 
> 
> -- 
> Arthur
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 



From stuart at lexacorp.com.pg  Sun Dec 19 21:56:53 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Mon, 20 Dec 2021 13:56:53 +1000
Subject: [AccessD] Alias Question
In-Reply-To: <61BFFE54.10861.1BDB5F39@stuart.lexacorp.com.pg>
References: <CAEPJO1i+Ds8xBtPdvCLDZ_OR=ZnbrfOrkKigzWFZMtZ6ZrsCng@mail.gmail.com>,
 <CAEPJO1hTsszrLbMX=rs9ztB3FfYYXK_W6sbxLPCpnacZjJoDrg@mail.gmail.com>,
 <61BFFE54.10861.1BDB5F39@stuart.lexacorp.com.pg>
Message-ID: <61BFFF05.24303.1BDE1476@stuart.lexacorp.com.pg>

Or you want different capitalisation to match your naming conventions.:

Declare Function GETDESKTOPWINDOW Lib "user32" ALIAS "GetDesktopWindow" () As Long
Declare Function getdesktopwindow Lib "user32" ALIAS "GetDesktopWindow" () As Long


On 20 Dec 2021 at 13:53, Stuart McLachlan wrote:

> Two possibilities:
> 1. If you want to abbreviate a long name, or 
> 2. If the original name of a function contains characters that are
> illegal in a function name in your development enviornment e.g.:
> DECLARE FUNCTION LegalName ALIAS "Illegal$Name" ... DECLARE FUNCTION
> LegalName ALIAS "3IllegalName" ... DECLARE FUNCTION LegalName ALIAS
> "_IllegalName" ...
> 
> 
> On 19 Dec 2021 at 22:04, Arthur Fuller wrote:
> 
> > The past that I am not understanding is why I would want to rename a
> > function unless it had a really long name that was a hassle to type.
> > 
> > On Sun, Dec 19, 2021 at 7:37 PM Stuart McLachlan
> > <stuart at lexacorp.com.pg> wrote:
> > 
> > > It's also worth noting that in VBA, you don't need an ALIAS if you
> > > don't rename the function:
> > >
> > > Declare Function GetDesktopWindow Lib "user32" () As Long
> > > ...
> > > Debug.Print GetDesktopWindow
> > > ...
> > >
> > > --
> > > Stuart
> > >
> > >
> > > On 19 Dec 2021 at 18:31, Arthur Fuller wrote:
> > >
> > > > Thanks Gary and Stuart. That clears things up.
> > > >
> > > > On Sun, Dec 19, 2021 at 5:53 PM Gary Kjos <garykjos at gmail.com>
> > > > wrote:
> > > >
> > > > > Here us Stuarts earlier long response Arthur.....
> > > > >
> > > > > On Sun, Dec 19, 2021 at 2:46 PM Stuart McLachlan
> > > > > <stuart at lexacorp.com.pg> wrote:
> > > > > >
> > > > > > It is the exact name of the function as the it appears in
> > > > > > the DLL. You
> > > > > can declare the
> > > > > > function with any function name you want in your code, but
> > > > > > you must give
> > > > > the correct actual
> > > > > > name, with correct capitalisation, as it appears in the
> > > > > > function as the
> > > > > ALIAS because that is
> > > > > > how your code finds it in the DLL.
> > > > > >
> > > > > > In your example, the actual exported function n the DLL is
> > > > > > called
> > > > > GetDesktopWindow (not
> > > > > > captialization).
> > > > > >
> > > > > > You could call get the Desktop WIndow handle with hWNd =
> > > > > > GetWinNAme() if
> > > > > you declared
> > > > > > your function like this:
> > > > > > Declare Function myGetWInName _
> > > > > > Lib "user32" Alias "GetDesktopWindow" () As Long
> > > > > >
> > > > > > If you did this (note incorrect capitalization), calling
> > > > > > your function
> > > > > would give an error since
> > > > > > their is no such function in the DLL.
> > > > > > Declare Function WM_apiGetDesktopWindow _
> > > > > > Lib "user32" Alias "Getdesktopwindow" () As Long
> > > > > >
> > > > > >
> > > > > >
> > > > > > On 19 Dec 2021 at 13:30, Arthur Fuller wrote:
> > > > > >
> > > > > > > Given a function declaration such as this(from ADH, by
> > > > > > > Getz et. al.): <code> Declare Function
> > > > > > > WM_apiGetDesktopWindow _ Lib "user32" Alias
> > > > > > > "GetDesktopWindow" () As Long </code>
> > > > > > >
> > > > > > > What purpose does the Alias serve?
> > > > > > >
> > > > > > > --
> > > > > > > Arthur
> > > > > > > --
> > > > > > > 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
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Gary Kjos
> > > > > garykjos at gmail.com
> > > > > --
> > > > > AccessD mailing list
> > > > > AccessD at databaseadvisors.com
> > > > > https://databaseadvisors.com/mailman/listinfo/accessd
> > > > > Website: http://www.databaseadvisors.com
> > > > >
> > > >
> > > >
> > > > --
> > > > Arthur
> > > > --
> > > > 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
> > >
> > 
> > 
> > -- 
> > Arthur
> > -- 
> > 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
> 



From fuller.artful at gmail.com  Mon Dec 20 05:20:13 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Mon, 20 Dec 2021 06:20:13 -0500
Subject: [AccessD] Alias Question
In-Reply-To: <61BFFF05.24303.1BDE1476@stuart.lexacorp.com.pg>
References: <CAEPJO1i+Ds8xBtPdvCLDZ_OR=ZnbrfOrkKigzWFZMtZ6ZrsCng@mail.gmail.com>
 <CAEPJO1hTsszrLbMX=rs9ztB3FfYYXK_W6sbxLPCpnacZjJoDrg@mail.gmail.com>
 <61BFFE54.10861.1BDB5F39@stuart.lexacorp.com.pg>
 <61BFFF05.24303.1BDE1476@stuart.lexacorp.com.pg>
Message-ID: <CAEPJO1hf3t2+DbnfAUFnDB70_TTs=FYifTarR8V62m2he7tgAA@mail.gmail.com>

That makes sense, stuart. Thanks.

On Sun, Dec 19, 2021 at 10:57 PM Stuart McLachlan <stuart at lexacorp.com.pg>
wrote:

> Or you want different capitalisation to match your naming conventions.:
>
> Declare Function GETDESKTOPWINDOW Lib "user32" ALIAS "GetDesktopWindow" ()
> As Long
> Declare Function getdesktopwindow Lib "user32" ALIAS "GetDesktopWindow" ()
> As Long
>
>
> On 20 Dec 2021 at 13:53, Stuart McLachlan wrote:
>
> > Two possibilities:
> > 1. If you want to abbreviate a long name, or
> > 2. If the original name of a function contains characters that are
> > illegal in a function name in your development enviornment e.g.:
> > DECLARE FUNCTION LegalName ALIAS "Illegal$Name" ... DECLARE FUNCTION
> > LegalName ALIAS "3IllegalName" ... DECLARE FUNCTION LegalName ALIAS
> > "_IllegalName" ...
> >
> >
> > On 19 Dec 2021 at 22:04, Arthur Fuller wrote:
> >
> > > The past that I am not understanding is why I would want to rename a
> > > function unless it had a really long name that was a hassle to type.
> > >
> > > On Sun, Dec 19, 2021 at 7:37 PM Stuart McLachlan
> > > <stuart at lexacorp.com.pg> wrote:
> > >
> > > > It's also worth noting that in VBA, you don't need an ALIAS if you
> > > > don't rename the function:
> > > >
> > > > Declare Function GetDesktopWindow Lib "user32" () As Long
> > > > ...
> > > > Debug.Print GetDesktopWindow
> > > > ...
> > > >
> > > > --
> > > > Stuart
> > > >
> > > >
> > > > On 19 Dec 2021 at 18:31, Arthur Fuller wrote:
> > > >
> > > > > Thanks Gary and Stuart. That clears things up.
> > > > >
> > > > > On Sun, Dec 19, 2021 at 5:53 PM Gary Kjos <garykjos at gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Here us Stuarts earlier long response Arthur.....
> > > > > >
> > > > > > On Sun, Dec 19, 2021 at 2:46 PM Stuart McLachlan
> > > > > > <stuart at lexacorp.com.pg> wrote:
> > > > > > >
> > > > > > > It is the exact name of the function as the it appears in
> > > > > > > the DLL. You
> > > > > > can declare the
> > > > > > > function with any function name you want in your code, but
> > > > > > > you must give
> > > > > > the correct actual
> > > > > > > name, with correct capitalisation, as it appears in the
> > > > > > > function as the
> > > > > > ALIAS because that is
> > > > > > > how your code finds it in the DLL.
> > > > > > >
> > > > > > > In your example, the actual exported function n the DLL is
> > > > > > > called
> > > > > > GetDesktopWindow (not
> > > > > > > captialization).
> > > > > > >
> > > > > > > You could call get the Desktop WIndow handle with hWNd =
> > > > > > > GetWinNAme() if
> > > > > > you declared
> > > > > > > your function like this:
> > > > > > > Declare Function myGetWInName _
> > > > > > > Lib "user32" Alias "GetDesktopWindow" () As Long
> > > > > > >
> > > > > > > If you did this (note incorrect capitalization), calling
> > > > > > > your function
> > > > > > would give an error since
> > > > > > > their is no such function in the DLL.
> > > > > > > Declare Function WM_apiGetDesktopWindow _
> > > > > > > Lib "user32" Alias "Getdesktopwindow" () As Long
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On 19 Dec 2021 at 13:30, Arthur Fuller wrote:
> > > > > > >
> > > > > > > > Given a function declaration such as this(from ADH, by
> > > > > > > > Getz et. al.): <code> Declare Function
> > > > > > > > WM_apiGetDesktopWindow _ Lib "user32" Alias
> > > > > > > > "GetDesktopWindow" () As Long </code>
> > > > > > > >
> > > > > > > > What purpose does the Alias serve?
> > > > > > > >
> > > > > > > > --
> > > > > > > > Arthur
> > > > > > > > --
> > > > > > > > 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
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Gary Kjos
> > > > > > garykjos at gmail.com
> > > > > > --
> > > > > > AccessD mailing list
> > > > > > AccessD at databaseadvisors.com
> > > > > > https://databaseadvisors.com/mailman/listinfo/accessd
> > > > > > Website: http://www.databaseadvisors.com
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Arthur
> > > > > --
> > > > > 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
> > > >
> > >
> > >
> > > --
> > > Arthur
> > > --
> > > 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
> >
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
Arthur

From fuller.artful at gmail.com  Tue Dec 21 12:17:34 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Tue, 21 Dec 2021 13:17:34 -0500
Subject: [AccessD] 32->64 bit conversion
Message-ID: <CAEPJO1hgVQo=p-sVzk6B6fELAUrF4bUSeZv076vu7kSwWW+ySw@mail.gmail.com>

This function is from ADH 2000 (Getz, Litwin et. al.):
<code>
Private Declare Function SendMessageStr _
 Lib "user32" Alias "SendMessageA" _
 (ByVal hwnd As Long, ByVal wMsg As Long, _
 ByVal wparam As Long, ByVal strName As String) As Long
</code>
Not surprisingly it's not in the PtrSafe file. I inserted the word PtrSafe
after the Declare  keyword. Judging by their names, I'm guessing that the
parameters  declared as Longs should be LongPtrs, and perhaps the return
value should be as well. Is that right?
Arthur

From fuller.artful at gmail.com  Tue Dec 21 19:41:12 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Tue, 21 Dec 2021 20:41:12 -0500
Subject: [AccessD] Handle v. Pointer
Message-ID: <CAEPJO1jnFqMyYsNU8V_XKXtD8aVFk5BnMpq+xMiejFPWZ1K_sQ@mail.gmail.com>

Is there a difference between a handle and a pointer? And if so, what?

--i
Arthur

From stuart at lexacorp.com.pg  Tue Dec 21 20:27:38 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Wed, 22 Dec 2021 12:27:38 +1000
Subject: [AccessD] Handle v. Pointer
In-Reply-To: <CAEPJO1jnFqMyYsNU8V_XKXtD8aVFk5BnMpq+xMiejFPWZ1K_sQ@mail.gmail.com>
References: <CAEPJO1jnFqMyYsNU8V_XKXtD8aVFk5BnMpq+xMiejFPWZ1K_sQ@mail.gmail.com>
Message-ID: <61C28D1A.19665.35CF778@stuart.lexacorp.com.pg>

A handle is a specific type of pointer.

A pointer is just a memory location.  (it "points" to the location)
A handle is a pointer to an object's memory location.

On 21 Dec 2021 at 20:41, Arthur Fuller wrote:

> Is there a difference between a handle and a pointer? And if so, what?
> 
> --i
> Arthur
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 



From stuart at lexacorp.com.pg  Tue Dec 21 20:46:52 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Wed, 22 Dec 2021 12:46:52 +1000
Subject: [AccessD] 32->64 bit conversion
In-Reply-To: <CAEPJO1hgVQo=p-sVzk6B6fELAUrF4bUSeZv076vu7kSwWW+ySw@mail.gmail.com>
References: <CAEPJO1hgVQo=p-sVzk6B6fELAUrF4bUSeZv076vu7kSwWW+ySw@mail.gmail.com>
Message-ID: <61C2919C.24096.36E90E7@stuart.lexacorp.com.pg>

Since strings in Access these days are all wide strings (Unicode - UTF-16), I'd change that 
to  Alias "SendMessageW" 

And yes HWnd,wMSg,wparam and the return value  are 32 bit or 64 bit depending on 
application and so should be LongPtrs.


On 21 Dec 2021 at 13:17, Arthur Fuller wrote:

> This function is from ADH 2000 (Getz, Litwin et. al.):
> <code>
> Private Declare Function SendMessageStr _
>  Lib "user32" Alias "SendMessageA" _
>  (ByVal hwnd As Long, ByVal wMsg As Long, _
>  ByVal wparam As Long, ByVal strName As String) As Long
> </code>
> Not surprisingly it's not in the PtrSafe file. I inserted the word
> PtrSafe after the Declare  keyword. Judging by their names, I'm
> guessing that the parameters  declared as Longs should be LongPtrs,
> and perhaps the return value should be as well. Is that right? Arthur
> -- AccessD mailing list AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd Website:
> http://www.databaseadvisors.com
> 



From stuart at lexacorp.com.pg  Tue Dec 21 22:25:36 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Wed, 22 Dec 2021 14:25:36 +1000
Subject: [AccessD] Handle v. Pointer
In-Reply-To: <61C28D1A.19665.35CF778@stuart.lexacorp.com.pg>
References: <CAEPJO1jnFqMyYsNU8V_XKXtD8aVFk5BnMpq+xMiejFPWZ1K_sQ@mail.gmail.com>,
 <61C28D1A.19665.35CF778@stuart.lexacorp.com.pg>
Message-ID: <61C2A8C0.1130.3C8F77B@stuart.lexacorp.com.pg>

Actually. that's not really true.  A handle is an abstraction of a pointer.  An object can move 
in memory, but it's handle won't change - the operating system maintains the relationship 
between a handle and where to find the object.
 


On 22 Dec 2021 at 12:27, Stuart McLachlan wrote:

> A handle is a specific type of pointer.
> 
> A pointer is just a memory location.  (it "points" to the location) A
> handle is a pointer to an object's memory location.
> 
> On 21 Dec 2021 at 20:41, Arthur Fuller wrote:
> 
> > Is there a difference between a handle and a pointer? And if so,
> > what?
> > 
> > --i
> > Arthur
> > -- 
> > 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
> 



From fuller.artful at gmail.com  Wed Dec 22 06:10:08 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Wed, 22 Dec 2021 07:10:08 -0500
Subject: [AccessD] Handle v. Pointer
In-Reply-To: <61C2A8C0.1130.3C8F77B@stuart.lexacorp.com.pg>
References: <CAEPJO1jnFqMyYsNU8V_XKXtD8aVFk5BnMpq+xMiejFPWZ1K_sQ@mail.gmail.com>
 <61C28D1A.19665.35CF778@stuart.lexacorp.com.pg>
 <61C2A8C0.1130.3C8F77B@stuart.lexacorp.com.pg>
Message-ID: <CAEPJO1ixHcVOT0N3EkS0L3cYL7vOrFbX4wQYK01oQx6mQKuotw@mail.gmail.com>

Thanks, Stuart. Now it makes sense.

On Tue, Dec 21, 2021 at 11:25 PM Stuart McLachlan <stuart at lexacorp.com.pg>
wrote:

> Actually. that's not really true.  A handle is an abstraction of a
> pointer.  An object can move
> in memory, but it's handle won't change - the operating system maintains
> the relationship
> between a handle and where to find the object.
>
>
>
> On 22 Dec 2021 at 12:27, Stuart McLachlan wrote:
>
> > A handle is a specific type of pointer.
> >
> > A pointer is just a memory location.  (it "points" to the location) A
> > handle is a pointer to an object's memory location.
> >
> > On 21 Dec 2021 at 20:41, Arthur Fuller wrote:
> >
> > > Is there a difference between a handle and a pointer? And if so,
> > > what?
> > >
> > > --i
> > > Arthur
> > > --
> > > 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
> >
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
Arthur

From fuller.artful at gmail.com  Wed Dec 22 06:14:12 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Wed, 22 Dec 2021 07:14:12 -0500
Subject: [AccessD] 32->64 bit conversion
In-Reply-To: <61C2919C.24096.36E90E7@stuart.lexacorp.com.pg>
References: <CAEPJO1hgVQo=p-sVzk6B6fELAUrF4bUSeZv076vu7kSwWW+ySw@mail.gmail.com>
 <61C2919C.24096.36E90E7@stuart.lexacorp.com.pg>
Message-ID: <CAEPJO1iE=obhwSo8mVSxdO-btLCuoW7NAF5oRyFfBuwLKfzh+w@mail.gmail.com>

Thanks, Stuart.\Looks like I'll have to do another pass through my updates
to adhCode.

On Tue, Dec 21, 2021 at 9:47 PM Stuart McLachlan <stuart at lexacorp.com.pg>
wrote:

> Since strings in Access these days are all wide strings (Unicode -
> UTF-16), I'd change that
> to  Alias "SendMessageW"
>
> And yes HWnd,wMSg,wparam and the return value  are 32 bit or 64 bit
> depending on
> application and so should be LongPtrs.
>
>
> On 21 Dec 2021 at 13:17, Arthur Fuller wrote:
>
> > This function is from ADH 2000 (Getz, Litwin et. al.):
> > <code>
> > Private Declare Function SendMessageStr _
> >  Lib "user32" Alias "SendMessageA" _
> >  (ByVal hwnd As Long, ByVal wMsg As Long, _
> >  ByVal wparam As Long, ByVal strName As String) As Long
> > </code>
> > Not surprisingly it's not in the PtrSafe file. I inserted the word
> > PtrSafe after the Declare  keyword. Judging by their names, I'm
> > guessing that the parameters  declared as Longs should be LongPtrs,
> > and perhaps the return value should be as well. Is that right? Arthur
> > -- 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
>


-- 
Arthur

From fuller.artful at gmail.com  Wed Dec 22 06:39:39 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Wed, 22 Dec 2021 07:39:39 -0500
Subject: [AccessD] Debug window gone away
Message-ID: <CAEPJO1gUegnfCbwiYBpd7z0d_EMFdqUmEePYvSKJNf2eW8JVWw@mail.gmail.com>

I've done something to make my debug window go away. Thanks to the keyboard
I'm using, Akt-F11 is complicated, and Ctrl_G apparently does nothing. Any
ideas?

-- 
Arthur

From Paul.W at industrialcontrol.co.nz  Wed Dec 22 14:21:51 2021
From: Paul.W at industrialcontrol.co.nz (Paul Wolstenholme)
Date: Thu, 23 Dec 2021 09:21:51 +1300
Subject: [AccessD] Debug window gone away
In-Reply-To: <CAEPJO1gUegnfCbwiYBpd7z0d_EMFdqUmEePYvSKJNf2eW8JVWw@mail.gmail.com>
References: <CAEPJO1gUegnfCbwiYBpd7z0d_EMFdqUmEePYvSKJNf2eW8JVWw@mail.gmail.com>
Message-ID: <CABGHdVnFgtNhHAWeE5dFjy2VdTaf+EQsvspoBw63EkONtjvhTQ@mail.gmail.com>

Arthur,

That is the expected behaviour when the open database is a runtime database
(.accdr) or has been renamed with the same extension as a runtime database
or when Access was opened with the command line parameter to invoke runtime
mode or when the version of Access installed on your computer is the (free)
runtime version.  Those are the situations I'm aware of and can remember
this morning.

Paul Wolstenholme

On Thu, 23 Dec 2021 at 01:40, Arthur Fuller <fuller.artful at gmail.com> wrote:

> I've done something to make my debug window go away. Thanks to the keyboard
> I'm using, Akt-F11 is complicated, and Ctrl_G apparently does nothing. Any
> ideas?
>
> --
> Arthur
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From fuller.artful at gmail.com  Wed Dec 22 14:40:56 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Wed, 22 Dec 2021 15:40:56 -0500
Subject: [AccessD] Debug window gone away
In-Reply-To: <CABGHdVnFgtNhHAWeE5dFjy2VdTaf+EQsvspoBw63EkONtjvhTQ@mail.gmail.com>
References: <CAEPJO1gUegnfCbwiYBpd7z0d_EMFdqUmEePYvSKJNf2eW8JVWw@mail.gmail.com>
 <CABGHdVnFgtNhHAWeE5dFjy2VdTaf+EQsvspoBw63EkONtjvhTQ@mail.gmail.com>
Message-ID: <CAEPJO1iJL6DOq4t-JQB=4qLcr_hdiSCscYDmiodUEi8ivaqu1w@mail.gmail.com>

Rhanks but none of those situations apply. However, you hace given me some
thought on this. Perhaps I;ll create a new ACCDB abd umoirt everything from
the old onem to see if that works

On Wed, Dec 22, 2021 at 3:23 PM Paul Wolstenholme <
Paul.W at industrialcontrol.co.nz> wrote:

> Arthur,
>
> That is the expected behaviour when the open database is a runtime database
> (.accdr) or has been renamed with the same extension as a runtime database
> or when Access was opened with the command line parameter to invoke runtime
> mode or when the version of Access installed on your computer is the (free)
> runtime version.  Those are the situations I'm aware of and can remember
> this morning.
>
> Paul Wolstenholme
>
> On Thu, 23 Dec 2021 at 01:40, Arthur Fuller <fuller.artful at gmail.com>
> wrote:
>
> > I've done something to make my debug window go away. Thanks to the
> keyboard
> > I'm using, Akt-F11 is complicated, and Ctrl_G apparently does nothing.
> Any
> > ideas?
> >
> > --
> > Arthur
> > --
> > 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
>


-- 
Arthur

From stuart at lexacorp.com.pg  Wed Dec 22 15:18:05 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Thu, 23 Dec 2021 07:18:05 +1000
Subject: [AccessD] 32->64 bit conversion
In-Reply-To: <CAEPJO1iE=obhwSo8mVSxdO-btLCuoW7NAF5oRyFfBuwLKfzh+w@mail.gmail.com>
References: <CAEPJO1hgVQo=p-sVzk6B6fELAUrF4bUSeZv076vu7kSwWW+ySw@mail.gmail.com>,
 <61C2919C.24096.36E90E7@stuart.lexacorp.com.pg>,
 <CAEPJO1iE=obhwSo8mVSxdO-btLCuoW7NAF5oRyFfBuwLKfzh+w@mail.gmail.com>
Message-ID: <61C3960D.26390.2560199@stuart.lexacorp.com.pg>

It's Line 6772 of Win32API_PtrSafe.TXT

Declare PtrSafe Function SendMessage Lib "user32" Alias "SendMessageA" (ByVal hwnd 
As LongPtr, ByVal wMsg As Long, ByVal wParam As LongPtr, lParam As Any) As LongPtr

I was mistaken, wparam is still declared as LONG, not LongPtr and it is declared as the  "A", 
function, not the "W"


On 22 Dec 2021 at 7:14, Arthur Fuller wrote:

> Thanks, Stuart.\Looks like I'll have to do another pass through my
> updates to adhCode.
> 
> On Tue, Dec 21, 2021 at 9:47 PM Stuart McLachlan
> <stuart at lexacorp.com.pg> wrote:
> 
> > Since strings in Access these days are all wide strings (Unicode -
> > UTF-16), I'd change that to  Alias "SendMessageW"
> >
> > And yes HWnd,wMSg,wparam and the return value  are 32 bit or 64 bit
> > depending on application and so should be LongPtrs.
> >
> >
> > On 21 Dec 2021 at 13:17, Arthur Fuller wrote:
> >
> > > This function is from ADH 2000 (Getz, Litwin et. al.):
> > > <code>
> > > Private Declare Function SendMessageStr _
> > >  Lib "user32" Alias "SendMessageA" _
> > >  (ByVal hwnd As Long, ByVal wMsg As Long, _
> > >  ByVal wparam As Long, ByVal strName As String) As Long
> > > </code>
> > > Not surprisingly it's not in the PtrSafe file. I inserted the word
> > > PtrSafe after the Declare  keyword. Judging by their names, I'm
> > > guessing that the parameters  declared as Longs should be
> > > LongPtrs, and perhaps the return value should be as well. Is that
> > > right? Arthur -- 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
> >
> 
> 
> -- 
> Arthur
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 



From stuart at lexacorp.com.pg  Wed Dec 22 15:33:52 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Thu, 23 Dec 2021 07:33:52 +1000
Subject: [AccessD] Debug window gone away
In-Reply-To: <CAEPJO1iJL6DOq4t-JQB=4qLcr_hdiSCscYDmiodUEi8ivaqu1w@mail.gmail.com>
References: <CAEPJO1gUegnfCbwiYBpd7z0d_EMFdqUmEePYvSKJNf2eW8JVWw@mail.gmail.com>,
 <CABGHdVnFgtNhHAWeE5dFjy2VdTaf+EQsvspoBw63EkONtjvhTQ@mail.gmail.com>,
 <CAEPJO1iJL6DOq4t-JQB=4qLcr_hdiSCscYDmiodUEi8ivaqu1w@mail.gmail.com>
Message-ID: <61C399C0.5009.2647619@stuart.lexacorp.com.pg>

Is there a grey border line above a thin blue line at the bottom of your VBE window?

If so, the immediate window has got itself minimized - it happens at times :(

Hover your mouse over the grey line and the cursor should change to the "vertical resize 
(up/down arrows with a double horizontal line) and you can drag it back into view.


On 22 Dec 2021 at 15:40, Arthur Fuller wrote:

> Rhanks but none of those situations apply. However, you hace given me
> some thought on this. Perhaps I;ll create a new ACCDB abd umoirt
> everything from the old onem to see if that works
> 
> On Wed, Dec 22, 2021 at 3:23 PM Paul Wolstenholme <
> Paul.W at industrialcontrol.co.nz> wrote:
> 
> > Arthur,
> >
> > That is the expected behaviour when the open database is a runtime
> > database (.accdr) or has been renamed with the same extension as a
> > runtime database or when Access was opened with the command line
> > parameter to invoke runtime mode or when the version of Access
> > installed on your computer is the (free) runtime version.  Those are
> > the situations I'm aware of and can remember this morning.
> >
> > Paul Wolstenholme
> >
> > On Thu, 23 Dec 2021 at 01:40, Arthur Fuller
> > <fuller.artful at gmail.com> wrote:
> >
> > > I've done something to make my debug window go away. Thanks to the
> > keyboard
> > > I'm using, Akt-F11 is complicated, and Ctrl_G apparently does
> > > nothing.
> > Any
> > > ideas?
> > >
> > > --
> > > Arthur
> > > --
> > > 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
> >
> 
> 
> -- 
> Arthur
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 



From stuart at lexacorp.com.pg  Wed Dec 22 15:43:07 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Thu, 23 Dec 2021 07:43:07 +1000
Subject: [AccessD] Debug window gone away
In-Reply-To: <61C399C0.5009.2647619@stuart.lexacorp.com.pg>
References: <CAEPJO1gUegnfCbwiYBpd7z0d_EMFdqUmEePYvSKJNf2eW8JVWw@mail.gmail.com>,
 <CAEPJO1iJL6DOq4t-JQB=4qLcr_hdiSCscYDmiodUEi8ivaqu1w@mail.gmail.com>,
 <61C399C0.5009.2647619@stuart.lexacorp.com.pg>
Message-ID: <61C39BEB.20097.26CED27@stuart.lexacorp.com.pg>

Another way to get it back - "Tools - Options - Docking" - Remove the check against 
"Immediate Window".   But if you check it again, it will re-dock itself minimzed at the bottom 
as before so you will still need to drag it back into view  :)

On 23 Dec 2021 at 7:33, Stuart McLachlan wrote:

> Is there a grey border line above a thin blue line at the bottom of
> your VBE window?
> 
> If so, the immediate window has got itself minimized - it happens at
> times :(
> 
> Hover your mouse over the grey line and the cursor should change to
> the "vertical resize (up/down arrows with a double horizontal line)
> and you can drag it back into view.
> 
> 
> On 22 Dec 2021 at 15:40, Arthur Fuller wrote:
> 
> > Rhanks but none of those situations apply. However, you hace given
> > me some thought on this. Perhaps I;ll create a new ACCDB abd umoirt
> > everything from the old onem to see if that works
> > 
> > On Wed, Dec 22, 2021 at 3:23 PM Paul Wolstenholme <
> > Paul.W at industrialcontrol.co.nz> wrote:
> > 
> > > Arthur,
> > >
> > > That is the expected behaviour when the open database is a runtime
> > > database (.accdr) or has been renamed with the same extension as a
> > > runtime database or when Access was opened with the command line
> > > parameter to invoke runtime mode or when the version of Access
> > > installed on your computer is the (free) runtime version.  Those
> > > are the situations I'm aware of and can remember this morning.
> > >
> > > Paul Wolstenholme
> > >
> > > On Thu, 23 Dec 2021 at 01:40, Arthur Fuller
> > > <fuller.artful at gmail.com> wrote:
> > >
> > > > I've done something to make my debug window go away. Thanks to
> > > > the
> > > keyboard
> > > > I'm using, Akt-F11 is complicated, and Ctrl_G apparently does
> > > > nothing.
> > > Any
> > > > ideas?
> > > >
> > > > --
> > > > Arthur
> > > > --
> > > > 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
> > >
> > 
> > 
> > -- 
> > Arthur
> > -- 
> > 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
> 



From fuller.artful at gmail.com  Thu Dec 23 12:06:13 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Thu, 23 Dec 2021 13:06:13 -0500
Subject: [AccessD] I'm drowning over here
Message-ID: <CAEPJO1jiFgNdfAED=j7gOZwYeZJmjickUsuUuA=xSe=PLWPefQ@mail.gmail.com>

Trying to solve the migration of adhCode to 64-bit and I am drowning. If
there is anyone on this list who has solved these dilemmas, I humbly ask
you to send me said files. I'm too old for this sort of aggravation. Back
in the day, I relished this sort of challenge. No more. I a 74 years old.
If there is anyone on this list who has been there and done that, I would
love it if you would send me your updated files, with everything converted
to 64 bit and also the conversions to LontPtr and LongLong, etc. I'm
drowning over here and need a paddle! Pease.

-- 
Arthur

From gustav at cactus.dk  Thu Dec 23 13:05:25 2021
From: gustav at cactus.dk (Gustav Brock)
Date: Thu, 23 Dec 2021 19:05:25 +0000
Subject: [AccessD] I'm drowning over here
In-Reply-To: <CAEPJO1jiFgNdfAED=j7gOZwYeZJmjickUsuUuA=xSe=PLWPefQ@mail.gmail.com>
References: <CAEPJO1jiFgNdfAED=j7gOZwYeZJmjickUsuUuA=xSe=PLWPefQ@mail.gmail.com>
Message-ID: <AS8PR10MB436024E1641B6F12A58F7AA3CA7E9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>

Hi Arthur

What is adhCode, please?

/gustav


Fra: Arthur Fuller<mailto:fuller.artful at gmail.com>
Sendt: 23. december 2021 19:06
Til: Access Developers discussion and problem solving<mailto:accessd at databaseadvisors.com>
Emne: [AccessD] I'm drowning over here

Trying to solve the migration of adhCode to 64-bit and I am drowning. If
there is anyone on this list who has solved these dilemmas, I humbly ask
you to send me said files. I'm too old for this sort of aggravation. Back
in the day, I relished this sort of challenge. No more. I a 74 years old.
If there is anyone on this list who has been there and done that, I would
love it if you would send me your updated files, with everything converted
to 64 bit and also the conversions to LontPtr and LongLong, etc. I'm
drowning over here and need a paddle! Pease.

--
Arthur


From martinreid at gmail.com  Thu Dec 23 13:11:28 2021
From: martinreid at gmail.com (Martin)
Date: Thu, 23 Dec 2021 19:11:28 +0000
Subject: [AccessD] I'm drowning over here
In-Reply-To: <AS8PR10MB436024E1641B6F12A58F7AA3CA7E9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
References: <CAEPJO1jiFgNdfAED=j7gOZwYeZJmjickUsuUuA=xSe=PLWPefQ@mail.gmail.com>
 <AS8PR10MB436024E1641B6F12A58F7AA3CA7E9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
Message-ID: <CAKyu+EXcdH7QO1CJ_Z=OXraVYw9JNZNv_h-P72kxtEAzNJ-ObA@mail.gmail.com>

Access developers handbook.

Arthur that's a serious bit of  code to convert?

Martin




On Thu, 23 Dec 2021, 19:05 Gustav Brock via AccessD, <
accessd at databaseadvisors.com> wrote:

> Hi Arthur
>
> What is adhCode, please?
>
> /gustav
>
>
> Fra: Arthur Fuller<mailto:fuller.artful at gmail.com>
> Sendt: 23. december 2021 19:06
> Til: Access Developers discussion and problem solving<mailto:
> accessd at databaseadvisors.com>
> Emne: [AccessD] I'm drowning over here
>
> Trying to solve the migration of adhCode to 64-bit and I am drowning. If
> there is anyone on this list who has solved these dilemmas, I humbly ask
> you to send me said files. I'm too old for this sort of aggravation. Back
> in the day, I relished this sort of challenge. No more. I a 74 years old.
> If there is anyone on this list who has been there and done that, I would
> love it if you would send me your updated files, with everything converted
> to 64 bit and also the conversions to LontPtr and LongLong, etc. I'm
> drowning over here and need a paddle! Pease.
>
> --
> Arthur
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From stuart at lexacorp.com.pg  Thu Dec 23 15:02:06 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Fri, 24 Dec 2021 07:02:06 +1000
Subject: [AccessD] I'm drowning over here
In-Reply-To: <CAEPJO1jiFgNdfAED=j7gOZwYeZJmjickUsuUuA=xSe=PLWPefQ@mail.gmail.com>
References: <CAEPJO1jiFgNdfAED=j7gOZwYeZJmjickUsuUuA=xSe=PLWPefQ@mail.gmail.com>
Message-ID: <61C4E3CE.8328.76DBC9A@stuart.lexacorp.com.pg>

That doesn't make sense.

The only things you should need to convert are any API Declarations.
They should all be in one location at the top of each module. How many different 
declarations are you talking about?



On 23 Dec 2021 at 13:06, Arthur Fuller wrote:

> Trying to solve the migration of adhCode to 64-bit and I am drowning.
> If there is anyone on this list who has solved these dilemmas, I
> humbly ask you to send me said files. I'm too old for this sort of
> aggravation. Back in the day, I relished this sort of challenge. No
> more. I a 74 years old. If there is anyone on this list who has been
> there and done that, I would love it if you would send me your updated
> files, with everything converted to 64 bit and also the conversions to
> LontPtr and LongLong, etc. I'm drowning over here and need a paddle!
> Pease.
> 
> -- 
> Arthur
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 



From gustav at cactus.dk  Thu Dec 23 15:30:55 2021
From: gustav at cactus.dk (Gustav Brock)
Date: Thu, 23 Dec 2021 21:30:55 +0000
Subject: [AccessD] I'm drowning over here
In-Reply-To: <CAKyu+EXcdH7QO1CJ_Z=OXraVYw9JNZNv_h-P72kxtEAzNJ-ObA@mail.gmail.com>
References: <CAEPJO1jiFgNdfAED=j7gOZwYeZJmjickUsuUuA=xSe=PLWPefQ@mail.gmail.com>
 <AS8PR10MB436024E1641B6F12A58F7AA3CA7E9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
 <CAKyu+EXcdH7QO1CJ_Z=OXraVYw9JNZNv_h-P72kxtEAzNJ-ObA@mail.gmail.com>
Message-ID: <AS8PR10MB43604EE79C1B6BBB8F438924CA7E9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>

Hi Arthur

Oh, but I don?t have that book and code, sorry.
But even if I had, you can?t possibly need every bit of it converted.

Post the bumps you may have encountered.

/gustav

Fra: Martin<mailto:martinreid at gmail.com>
Sendt: 23. december 2021 20:11
Til: Access Developers discussion and problem solving<mailto:accessd at databaseadvisors.com>
Emne: Re: [AccessD] I'm drowning over here

Access developers handbook.

Arthur that's a serious bit of  code to convert?

Martin

On Thu, 23 Dec 2021, 19:05 Gustav Brock via AccessD, <
accessd at databaseadvisors.com> wrote:

> Hi Arthur
>
> What is adhCode, please?
>
> /gustav
>
>
> Fra: Arthur Fuller<mailto:fuller.artful at gmail.com>
> Sendt: 23. december 2021 19:06
> Til: Access Developers discussion and problem solving<mailto:
> accessd at databaseadvisors.com>
> Emne: [AccessD] I'm drowning over here
>
> Trying to solve the migration of adhCode to 64-bit and I am drowning. If
> there is anyone on this list who has solved these dilemmas, I humbly ask
> you to send me said files. I'm too old for this sort of aggravation. Back
> in the day, I relished this sort of challenge. No more. I a 74 years old.
> If there is anyone on this list who has been there and done that, I would
> love it if you would send me your updated files, with everything converted
> to 64 bit and also the conversions to LontPtr and LongLong, etc. I'm
> drowning over here and need a paddle! Pease.
>
> --
> Arthur

From James at charltonweeks.com  Thu Dec 23 16:04:00 2021
From: James at charltonweeks.com (James Charlton)
Date: Thu, 23 Dec 2021 22:04:00 +0000
Subject: [AccessD] Converting to 64 Bit
Message-ID: <BYAPR05MB49834B7258AD573E6694E663AB7E9@BYAPR05MB4983.namprd05.prod.outlook.com>

My partner is convinced that sooner or later Microsoft Office will be exclusively 64 bit and therefore, sooner or later, our Access mdb needs to be converted.  I spoke with Rocky who expressed disbelief in that assessment.  What say you all?
jc

James Charlton
Charlton Weeks LLP
1031 W Ave M14, Suite A
Palmdale, CA 93551
661-265-0969


From gustav at cactus.dk  Thu Dec 23 16:10:51 2021
From: gustav at cactus.dk (Gustav Brock)
Date: Thu, 23 Dec 2021 22:10:51 +0000
Subject: [AccessD] Converting to 64 Bit
In-Reply-To: <BYAPR05MB49834B7258AD573E6694E663AB7E9@BYAPR05MB4983.namprd05.prod.outlook.com>
References: <BYAPR05MB49834B7258AD573E6694E663AB7E9@BYAPR05MB4983.namprd05.prod.outlook.com>
Message-ID: <AS8PR10MB43603B0C81A02F4F8D124DBBCA7E9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>

Hi James

32-bit will probably exist as long Windows 10 is supported. Until now, however, Windows 11 seems only to exist as 64-bit.

But, as all new machines default to 64-bit Windows 10/11, there is no reason to postpone the conversion of your database to 64-bit. If you don?t use fancy 32-bit-only ActiveX controls, most likely, it will be no-brainer.

/gustav

Fra: James Charlton<mailto:James at charltonweeks.com>
Sendt: 23. december 2021 23:04
Til: Access Developers discussion and problem solving<mailto:accessd at databaseadvisors.com>
Emne: [AccessD] Converting to 64 Bit

My partner is convinced that sooner or later Microsoft Office will be exclusively 64 bit and therefore, sooner or later, our Access mdb needs to be converted.  I spoke with Rocky who expressed disbelief in that assessment.  What say you all?
jc

James Charlton
Charlton Weeks LLP
1031 W Ave M14, Suite A
Palmdale, CA 93551
661-265-0969

From stuart at lexacorp.com.pg  Thu Dec 23 17:00:53 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Fri, 24 Dec 2021 09:00:53 +1000
Subject: [AccessD] Converting to 64 Bit
In-Reply-To: <BYAPR05MB49834B7258AD573E6694E663AB7E9@BYAPR05MB4983.namprd05.prod.outlook.com>
References: <BYAPR05MB49834B7258AD573E6694E663AB7E9@BYAPR05MB4983.namprd05.prod.outlook.com>
Message-ID: <61C4FFA5.17569.7DA7658@stuart.lexacorp.com.pg>

32bit Office is not going away any time soon.  That said:

Is your application really a .mdb?

If so, it's more important to convert it to accdb rather than worry about 32/64 bit at this 
stage.

Is "your Access mdb" just for your own use? DO you have control over the machines it is 
run on?

The default Office installation in now 64bit and consequently any new machine is likely to 
have 64bit Office - so even though 32bit is still going to be around for quite a while, having 
your Access appl;ication 64bit compatible makes  a lot of sense.




On 23 Dec 2021 at 22:04, James Charlton wrote:

> My partner is convinced that sooner or later Microsoft Office will be
> exclusively 64 bit and therefore, sooner or later, our Access mdb
> needs to be converted.  I spoke with Rocky who expressed disbelief in
> that assessment.  What say you all? jc
> 
> James Charlton
> Charlton Weeks LLP
> 1031 W Ave M14, Suite A
> Palmdale, CA 93551
> 661-265-0969
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 



From rockysmolin2 at gmail.com  Thu Dec 23 18:59:47 2021
From: rockysmolin2 at gmail.com (Rocky Smolin)
Date: Thu, 23 Dec 2021 16:59:47 -0800
Subject: [AccessD] Converting to 64 Bit
In-Reply-To: <AS8PR10MB43603B0C81A02F4F8D124DBBCA7E9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
References: <BYAPR05MB49834B7258AD573E6694E663AB7E9@BYAPR05MB4983.namprd05.prod.outlook.com>
 <AS8PR10MB43603B0C81A02F4F8D124DBBCA7E9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
Message-ID: <CAEcmsdBFfcTHG2pNTM9wNxh3E4_vMojHy6PqqKa_CKyfgoWQzQ@mail.gmail.com>

What would your recommendation be in an environment with both 32 and 64 bit
Office installed? Upgrade everyone to 64 bit?  Or have two versions of the
app?

r

On Thu, Dec 23, 2021 at 2:10 PM Gustav Brock via AccessD <
accessd at databaseadvisors.com> wrote:

> Hi James
>
> 32-bit will probably exist as long Windows 10 is supported. Until now,
> however, Windows 11 seems only to exist as 64-bit.
>
> But, as all new machines default to 64-bit Windows 10/11, there is no
> reason to postpone the conversion of your database to 64-bit. If you don?t
> use fancy 32-bit-only ActiveX controls, most likely, it will be no-brainer.
>
> /gustav
>
> Fra: James Charlton<mailto:James at charltonweeks.com>
> Sendt: 23. december 2021 23:04
> Til: Access Developers discussion and problem solving<mailto:
> accessd at databaseadvisors.com>
> Emne: [AccessD] Converting to 64 Bit
>
> My partner is convinced that sooner or later Microsoft Office will be
> exclusively 64 bit and therefore, sooner or later, our Access mdb needs to
> be converted.  I spoke with Rocky who expressed disbelief in that
> assessment.  What say you all?
> jc
>
> James Charlton
> Charlton Weeks LLP
> 1031 W Ave M14, Suite A
> Palmdale, CA 93551
> 661-265-0969
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From stuart at lexacorp.com.pg  Thu Dec 23 20:52:35 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Fri, 24 Dec 2021 12:52:35 +1000
Subject: [AccessD] Converting to 64 Bit
In-Reply-To: <CAEcmsdBFfcTHG2pNTM9wNxh3E4_vMojHy6PqqKa_CKyfgoWQzQ@mail.gmail.com>
References: <BYAPR05MB49834B7258AD573E6694E663AB7E9@BYAPR05MB4983.namprd05.prod.outlook.com>,
 <AS8PR10MB43603B0C81A02F4F8D124DBBCA7E9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>,
 <CAEcmsdBFfcTHG2pNTM9wNxh3E4_vMojHy6PqqKa_CKyfgoWQzQ@mail.gmail.com>
Message-ID: <61C535F3.1923.8AE9737@stuart.lexacorp.com.pg>

Depends on the organisation and the security requirements. :)

If they have their own FEs and they are .accdb then it doesn't matter.  One size fits alll.

If you want users to have accde, then you either upgrade everyone (which may be costly if 
you have old workstations and old versions of Office) or you have two compiled versions.   

I've got clients in both scenarios, but as old machines are replaced and office versions are 
upgraded, they generally evolve to all 64 bit.

(The only proviso is if you are using any 32bit extrenal liraries of add-ons, you have to stick 
with 32bit Access).



On 23 Dec 2021 at 16:59, Rocky Smolin wrote:

> What would your recommendation be in an environment with both 32 and
> 64 bit Office installed? Upgrade everyone to 64 bit?  Or have two
> versions of the app?
> 
> r
> 
> On Thu, Dec 23, 2021 at 2:10 PM Gustav Brock via AccessD <
> accessd at databaseadvisors.com> wrote:
> 
> > Hi James
> >
> > 32-bit will probably exist as long Windows 10 is supported. Until
> > now, however, Windows 11 seems only to exist as 64-bit.
> >
> > But, as all new machines default to 64-bit Windows 10/11, there is
> > no reason to postpone the conversion of your database to 64-bit. If
> > you don?t use fancy 32-bit-only ActiveX controls, most likely, it
> > will be no-brainer.
> >
> > /gustav
> >
> > Fra: James Charlton<mailto:James at charltonweeks.com>
> > Sendt: 23. december 2021 23:04
> > Til: Access Developers discussion and problem solving<mailto:
> > accessd at databaseadvisors.com>
> > Emne: [AccessD] Converting to 64 Bit
> >
> > My partner is convinced that sooner or later Microsoft Office will
> > be exclusively 64 bit and therefore, sooner or later, our Access mdb
> > needs to be converted.  I spoke with Rocky who expressed disbelief
> > in that assessment.  What say you all? jc
> >
> > James Charlton
> > Charlton Weeks LLP
> > 1031 W Ave M14, Suite A
> > Palmdale, CA 93551
> > 661-265-0969
> > --
> > 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



From gustav at cactus.dk  Fri Dec 24 06:58:16 2021
From: gustav at cactus.dk (Gustav Brock)
Date: Fri, 24 Dec 2021 12:58:16 +0000
Subject: [AccessD] OT: Merry Christmas
In-Reply-To: <HE1PR10MB1692C7CFD1F4DEF39460BC7CCADD0@HE1PR10MB1692.EURPRD10.PROD.OUTLOOK.COM>
References: <HE1PR10MB0427ECCFBEE8DA866AB0FA6ECABB0@HE1PR10MB0427.EURPRD10.PROD.OUTLOOK.COM>
 <HE1PR10MB1692C7CFD1F4DEF39460BC7CCADD0@HE1PR10MB1692.EURPRD10.PROD.OUTLOOK.COM>
Message-ID: <AS8PR10MB43601D91AB1416BDE186985BCA7F9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>

Hi all, including the faithful lurkers

Last year was strange, but this year the vaccines are out. Still, no one can feel completely safe, indeed not the anti-vaccers, which I will never learn to understand.

I hope you take your precautions to stay safe, and that you will enjoy a merry Christmas and a happy New Year!
Gustav


From anita at ddisolutions.com.au  Fri Dec 24 07:04:49 2021
From: anita at ddisolutions.com.au (Anita Smith)
Date: Fri, 24 Dec 2021 13:04:49 +0000
Subject: [AccessD] OT: Merry Christmas
In-Reply-To: <AS8PR10MB43601D91AB1416BDE186985BCA7F9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
References: <HE1PR10MB0427ECCFBEE8DA866AB0FA6ECABB0@HE1PR10MB0427.EURPRD10.PROD.OUTLOOK.COM>
 <HE1PR10MB1692C7CFD1F4DEF39460BC7CCADD0@HE1PR10MB1692.EURPRD10.PROD.OUTLOOK.COM>
 <AS8PR10MB43601D91AB1416BDE186985BCA7F9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
Message-ID: <SYBP282MB0475E4237F9CAFB1BBEE8E52FF7F9@SYBP282MB0475.AUSP282.PROD.OUTLOOK.COM>

Merry Christmas to you and yours.

Looks like it's a white one for you.

Let's hope 2022 is a better year for us all.

Anita



-------- Original message --------
From: Gustav Brock via AccessD <accessd at databaseadvisors.com>
Date: 24/12/21 11:58 pm (GMT+10:00)
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Cc: Gustav Brock <gustav at cactus.dk>
Subject: [AccessD] OT: Merry Christmas

Hi all, including the faithful lurkers

Last year was strange, but this year the vaccines are out. Still, no one can feel completely safe, indeed not the anti-vaccers, which I will never learn to understand.

I hope you take your precautions to stay safe, and that you will enjoy a merry Christmas and a happy New Year!
Gustav

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

From jackandpat.d at gmail.com  Fri Dec 24 07:18:26 2021
From: jackandpat.d at gmail.com (jack drawbridge)
Date: Fri, 24 Dec 2021 08:18:26 -0500
Subject: [AccessD] OT: Merry Christmas
In-Reply-To: <SYBP282MB0475E4237F9CAFB1BBEE8E52FF7F9@SYBP282MB0475.AUSP282.PROD.OUTLOOK.COM>
References: <HE1PR10MB0427ECCFBEE8DA866AB0FA6ECABB0@HE1PR10MB0427.EURPRD10.PROD.OUTLOOK.COM>
 <HE1PR10MB1692C7CFD1F4DEF39460BC7CCADD0@HE1PR10MB1692.EURPRD10.PROD.OUTLOOK.COM>
 <AS8PR10MB43601D91AB1416BDE186985BCA7F9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
 <SYBP282MB0475E4237F9CAFB1BBEE8E52FF7F9@SYBP282MB0475.AUSP282.PROD.OUTLOOK.COM>
Message-ID: <CAKvidAsvrg_cWKZ93Ho87qAti3bSq202+bE=W=0ZibQXPPjuqQ@mail.gmail.com>

Merry Christmas to all from Canada. White with freezing rain in the
forecast here. Let's hope 2022 will be a major improvement and more normal
than 2020 and 2021.
Stay healthy!

jack



On Fri, Dec 24, 2021 at 8:05 AM Anita Smith <anita at ddisolutions.com.au>
wrote:

> Merry Christmas to you and yours.
>
> Looks like it's a white one for you.
>
> Let's hope 2022 is a better year for us all.
>
> Anita
>
>
>
> -------- Original message --------
> From: Gustav Brock via AccessD <accessd at databaseadvisors.com>
> Date: 24/12/21 11:58 pm (GMT+10:00)
> To: Access Developers discussion and problem solving <
> accessd at databaseadvisors.com>
> Cc: Gustav Brock <gustav at cactus.dk>
> Subject: [AccessD] OT: Merry Christmas
>
> Hi all, including the faithful lurkers
>
> Last year was strange, but this year the vaccines are out. Still, no one
> can feel completely safe, indeed not the anti-vaccers, which I will never
> learn to understand.
>
> I hope you take your precautions to stay safe, and that you will enjoy a
> merry Christmas and a happy New Year!
> Gustav
>
> --
> 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
>

From garykjos at gmail.com  Fri Dec 24 07:22:54 2021
From: garykjos at gmail.com (Gary Kjos)
Date: Fri, 24 Dec 2021 07:22:54 -0600
Subject: [AccessD] OT: Merry Christmas
In-Reply-To: <AS8PR10MB43601D91AB1416BDE186985BCA7F9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
References: <HE1PR10MB0427ECCFBEE8DA866AB0FA6ECABB0@HE1PR10MB0427.EURPRD10.PROD.OUTLOOK.COM>
 <HE1PR10MB1692C7CFD1F4DEF39460BC7CCADD0@HE1PR10MB1692.EURPRD10.PROD.OUTLOOK.COM>
 <AS8PR10MB43601D91AB1416BDE186985BCA7F9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
Message-ID: <CAJ2R_p+q8OcRPCT3XnzQHQZsKiyhWFw9_23NcZt4vG6RH17CiQ@mail.gmail.com>

Merry Christmas from Minnesota AccessD!

Stay healthy and happy!

GK

On Fri, Dec 24, 2021 at 6:58 AM Gustav Brock via AccessD
<accessd at databaseadvisors.com> wrote:
>
> Hi all, including the faithful lurkers
>
> Last year was strange, but this year the vaccines are out. Still, no one can feel completely safe, indeed not the anti-vaccers, which I will never learn to understand.
>
> I hope you take your precautions to stay safe, and that you will enjoy a merry Christmas and a happy New Year!
> Gustav
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com



-- 
Gary Kjos
garykjos at gmail.com

From randall.anthony at cox.net  Fri Dec 24 07:24:00 2021
From: randall.anthony at cox.net (Randall Anthony)
Date: Fri, 24 Dec 2021 08:24:00 -0500
Subject: [AccessD] OT: Merry Christmas
In-Reply-To: <CAJ2R_p+q8OcRPCT3XnzQHQZsKiyhWFw9_23NcZt4vG6RH17CiQ@mail.gmail.com>
References: <HE1PR10MB0427ECCFBEE8DA866AB0FA6ECABB0@HE1PR10MB0427.EURPRD10.PROD.OUTLOOK.COM>
 <HE1PR10MB1692C7CFD1F4DEF39460BC7CCADD0@HE1PR10MB1692.EURPRD10.PROD.OUTLOOK.COM>
 <AS8PR10MB43601D91AB1416BDE186985BCA7F9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
 <CAJ2R_p+q8OcRPCT3XnzQHQZsKiyhWFw9_23NcZt4vG6RH17CiQ@mail.gmail.com>
Message-ID: <086d01d7f8c9$84e39020$8eaab060$@cox.net>

Merry Christmas everyone!

-----Original Message-----
From: AccessD <accessd-bounces+randall.anthony=cox.net at databaseadvisors.com>
On Behalf Of Gary Kjos
Sent: Friday, December 24, 2021 8:23 AM
To: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] OT: Merry Christmas

Merry Christmas from Minnesota AccessD!

Stay healthy and happy!

GK

On Fri, Dec 24, 2021 at 6:58 AM Gustav Brock via AccessD
<accessd at databaseadvisors.com> wrote:
>
> Hi all, including the faithful lurkers
>
> Last year was strange, but this year the vaccines are out. Still, no one
can feel completely safe, indeed not the anti-vaccers, which I will never
learn to understand.
>
> I hope you take your precautions to stay safe, and that you will enjoy a
merry Christmas and a happy New Year!
> Gustav
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com



--
Gary Kjos
garykjos at gmail.com
--
AccessD mailing list
AccessD at databaseadvisors.com
https://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


-- 
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


From martinreid at gmail.com  Fri Dec 24 08:04:14 2021
From: martinreid at gmail.com (Martin)
Date: Fri, 24 Dec 2021 14:04:14 +0000
Subject: [AccessD] OT: Merry Christmas
In-Reply-To: <086d01d7f8c9$84e39020$8eaab060$@cox.net>
References: <HE1PR10MB0427ECCFBEE8DA866AB0FA6ECABB0@HE1PR10MB0427.EURPRD10.PROD.OUTLOOK.COM>
 <HE1PR10MB1692C7CFD1F4DEF39460BC7CCADD0@HE1PR10MB1692.EURPRD10.PROD.OUTLOOK.COM>
 <AS8PR10MB43601D91AB1416BDE186985BCA7F9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
 <CAJ2R_p+q8OcRPCT3XnzQHQZsKiyhWFw9_23NcZt4vG6RH17CiQ@mail.gmail.com>
 <086d01d7f8c9$84e39020$8eaab060$@cox.net>
Message-ID: <CAKyu+EV+Awq01ny97rfW0oxC+FiTVk__47twQvDmoW_fRD--Dg@mail.gmail.com>

Merry Christmas everyone from rainy Ireland.

Martin

On Fri, 24 Dec 2021, 13:24 Randall Anthony, <randall.anthony at cox.net> wrote:

> Merry Christmas everyone!
>
> -----Original Message-----
> From: AccessD <accessd-bounces+randall.anthony=
> cox.net at databaseadvisors.com>
> On Behalf Of Gary Kjos
> Sent: Friday, December 24, 2021 8:23 AM
> To: Access Developers discussion and problem solving
> <accessd at databaseadvisors.com>
> Subject: Re: [AccessD] OT: Merry Christmas
>
> Merry Christmas from Minnesota AccessD!
>
> Stay healthy and happy!
>
> GK
>
> On Fri, Dec 24, 2021 at 6:58 AM Gustav Brock via AccessD
> <accessd at databaseadvisors.com> wrote:
> >
> > Hi all, including the faithful lurkers
> >
> > Last year was strange, but this year the vaccines are out. Still, no one
> can feel completely safe, indeed not the anti-vaccers, which I will never
> learn to understand.
> >
> > I hope you take your precautions to stay safe, and that you will enjoy a
> merry Christmas and a happy New Year!
> > Gustav
> >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
>
>
>
> --
> Gary Kjos
> garykjos at gmail.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>
> --
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From hkotsch at arcor.de  Fri Dec 24 08:42:04 2021
From: hkotsch at arcor.de (Helmut Kotsch)
Date: Fri, 24 Dec 2021 15:42:04 +0100
Subject: [AccessD] OT: Merry Christmas
In-Reply-To: <CAKyu+EV+Awq01ny97rfW0oxC+FiTVk__47twQvDmoW_fRD--Dg@mail.gmail.com>
References: <HE1PR10MB0427ECCFBEE8DA866AB0FA6ECABB0@HE1PR10MB0427.EURPRD10.PROD.OUTLOOK.COM>
 <HE1PR10MB1692C7CFD1F4DEF39460BC7CCADD0@HE1PR10MB1692.EURPRD10.PROD.OUTLOOK.COM>
 <AS8PR10MB43601D91AB1416BDE186985BCA7F9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
 <CAJ2R_p+q8OcRPCT3XnzQHQZsKiyhWFw9_23NcZt4vG6RH17CiQ@mail.gmail.com>
 <086d01d7f8c9$84e39020$8eaab060$@cox.net>
 <CAKyu+EV+Awq01ny97rfW0oxC+FiTVk__47twQvDmoW_fRD--Dg@mail.gmail.com>
Message-ID: <006501d7f8d4$6d2fbfc0$478f3f40$@de>

Merry Christmas and a happy New Year from Mainz (the City of BioNTech)
Germany!

Helmut

-----Urspr?ngliche Nachricht-----
Von: AccessD [mailto:accessd-bounces+hkotsch=arcor.de at databaseadvisors.com]
Im Auftrag von Martin
Gesendet: Freitag, 24. Dezember 2021 15:04
An: Access Developers discussion and problem solving
Betreff: Re: [AccessD] OT: Merry Christmas

Merry Christmas everyone from rainy Ireland.

Martin

On Fri, 24 Dec 2021, 13:24 Randall Anthony, <randall.anthony at cox.net> wrote:

> Merry Christmas everyone!
>
> -----Original Message-----
> From: AccessD <accessd-bounces+randall.anthony=
> cox.net at databaseadvisors.com>
> On Behalf Of Gary Kjos
> Sent: Friday, December 24, 2021 8:23 AM
> To: Access Developers discussion and problem solving
> <accessd at databaseadvisors.com>
> Subject: Re: [AccessD] OT: Merry Christmas
>
> Merry Christmas from Minnesota AccessD!
>
> Stay healthy and happy!
>
> GK
>
> On Fri, Dec 24, 2021 at 6:58 AM Gustav Brock via AccessD
> <accessd at databaseadvisors.com> wrote:
> >
> > Hi all, including the faithful lurkers
> >
> > Last year was strange, but this year the vaccines are out. Still, no one
> can feel completely safe, indeed not the anti-vaccers, which I will never
> learn to understand.
> >
> > I hope you take your precautions to stay safe, and that you will enjoy a
> merry Christmas and a happy New Year!
> > Gustav
> >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
>
>
>
> --
> Gary Kjos
> garykjos at gmail.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>
> --
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
> --
> 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


From fuller.artful at gmail.com  Fri Dec 24 09:30:51 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Fri, 24 Dec 2021 10:30:51 -0500
Subject: [AccessD] How to maximize the Reply window in Gmail?
Message-ID: <CAEPJO1jo8b36MrSvqTORoOwPatG2Tyr=7dcph_J3A1+MFHydzg@mail.gmail.com>

Once in a while, I have fluked this View, but am unable to repeat it.
Actually, that's just a way around my bigger problem: Gmail insists o
popping up this toolbar continuing various symbols such as Undo and Redo
and various things like font-selection, Bold, Italics, etc. O wish I could
dismiss this sonofabitch forever, but cannot figure out how to do that,
short of killing Gmail and installing Thunderbird instead. Pay attention,
you authors of Gmail! The users are very unhappy. Thanks a lot for your
"Help".

-- 
Arthur

From fuller.artful at gmail.com  Fri Dec 24 11:14:45 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Fri, 24 Dec 2021 12:14:45 -0500
Subject: [AccessD] Converting to 64 Bit
In-Reply-To: <61C535F3.1923.8AE9737@stuart.lexacorp.com.pg>
References: <BYAPR05MB49834B7258AD573E6694E663AB7E9@BYAPR05MB4983.namprd05.prod.outlook.com>
 <AS8PR10MB43603B0C81A02F4F8D124DBBCA7E9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
 <CAEcmsdBFfcTHG2pNTM9wNxh3E4_vMojHy6PqqKa_CKyfgoWQzQ@mail.gmail.com>
 <61C535F3.1923.8AE9737@stuart.lexacorp.com.pg>
Message-ID: <CAEPJO1jq+szsRP1uVqGVxCCUXqfDnrEczCCpQKL2ZfezYG+Vjg@mail.gmail.com>

Stuart,

How did you get so smart? Is it the air in NPG?

As for the 32->64 bt conversion, I cannot believe how llong this is taking.
I keep thinking that I'm almost done, but then another insect bites me.
Eventually I will bite baack all those insects, and when I'm done I will
post the new files on my web site, so that no one else has to suffer this
crap.

On Thu, Dec 23, 2021 at 9:52 PM Stuart McLachlan <stuart at lexacorp.com.pg>
wrote:

> Depends on the organisation and the security requirements. :)
>
> If they have their own FEs and they are .accdb then it doesn't matter.
> One size fits alll.
>
> If you want users to have accde, then you either upgrade everyone (which
> may be costly if
> you have old workstations and old versions of Office) or you have two
> compiled versions.
>
> I've got clients in both scenarios, but as old machines are replaced and
> office versions are
> upgraded, they generally evolve to all 64 bit.
>
> (The only proviso is if you are using any 32bit extrenal liraries of
> add-ons, you have to stick
> with 32bit Access).
>
>
>
> On 23 Dec 2021 at 16:59, Rocky Smolin wrote:
>
> > What would your recommendation be in an environment with both 32 and
> > 64 bit Office installed? Upgrade everyone to 64 bit?  Or have two
> > versions of the app?
> >
> > r
> >
> > On Thu, Dec 23, 2021 at 2:10 PM Gustav Brock via AccessD <
> > accessd at databaseadvisors.com> wrote:
> >
> > > Hi James
> > >
> > > 32-bit will probably exist as long Windows 10 is supported. Until
> > > now, however, Windows 11 seems only to exist as 64-bit.
> > >
> > > But, as all new machines default to 64-bit Windows 10/11, there is
> > > no reason to postpone the conversion of your database to 64-bit. If
> > > you don?t use fancy 32-bit-only ActiveX controls, most likely, it
> > > will be no-brainer.
> > >
> > > /gustav
> > >
> > > Fra: James Charlton<mailto:James at charltonweeks.com>
> > > Sendt: 23. december 2021 23:04
> > > Til: Access Developers discussion and problem solving<mailto:
> > > accessd at databaseadvisors.com>
> > > Emne: [AccessD] Converting to 64 Bit
> > >
> > > My partner is convinced that sooner or later Microsoft Office will
> > > be exclusively 64 bit and therefore, sooner or later, our Access mdb
> > > needs to be converted.  I spoke with Rocky who expressed disbelief
> > > in that assessment.  What say you all? jc
> > >
> > > James Charlton
> > > Charlton Weeks LLP
> > > 1031 W Ave M14, Suite A
> > > Palmdale, CA 93551
> > > 661-265-0969
> > > --
> > > 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
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
Arthur

From rockysmolin2 at gmail.com  Fri Dec 24 11:43:03 2021
From: rockysmolin2 at gmail.com (Rocky Smolin)
Date: Fri, 24 Dec 2021 09:43:03 -0800
Subject: [AccessD] Fwd: Merry Christmas
In-Reply-To: <CAEcmsdCGvs+AgogM+XcQcKqbVnZyJ4UvrxfgcWAT=1hSp=ShUg@mail.gmail.com>
References: <CAEcmsdCGvs+AgogM+XcQcKqbVnZyJ4UvrxfgcWAT=1hSp=ShUg@mail.gmail.com>
Message-ID: <CAEcmsdAJUKLbai+VWMqPeHP62ae1O5OujSX3kStJsJwuWNW2XQ@mail.gmail.com>

Merry Christmas to all and a Happy New Year from Carlsbad in sunny Southern
California where it's rainy and cold right now (so cold I have to wear
socks!). Stay well this coming year.

Best,

Rocky

From paulrster at gmail.com  Fri Dec 24 15:50:02 2021
From: paulrster at gmail.com (paul)
Date: Fri, 24 Dec 2021 21:50:02 +0000
Subject: [AccessD] Converting to 64 Bit
In-Reply-To: <CAEPJO1jq+szsRP1uVqGVxCCUXqfDnrEczCCpQKL2ZfezYG+Vjg@mail.gmail.com>
References: <BYAPR05MB49834B7258AD573E6694E663AB7E9@BYAPR05MB4983.namprd05.prod.outlook.com>
 <AS8PR10MB43603B0C81A02F4F8D124DBBCA7E9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
 <CAEcmsdBFfcTHG2pNTM9wNxh3E4_vMojHy6PqqKa_CKyfgoWQzQ@mail.gmail.com>
 <61C535F3.1923.8AE9737@stuart.lexacorp.com.pg>
 <CAEPJO1jq+szsRP1uVqGVxCCUXqfDnrEczCCpQKL2ZfezYG+Vjg@mail.gmail.com>
Message-ID: <CAKoNfVvQ56U+QG5sSDBOsMbHD28GqrApmPG0_8VQc+6eJq+4TA@mail.gmail.com>

Wishing you a great Christmas, Arthur. Hope it's all going really well for
you.
And hoping for a really good New Year's eve for you, leading into an
excellent year.

Best of best Christmas wishes

Paul





On Fri, 24 Dec 2021 at 17:15, Arthur Fuller <fuller.artful at gmail.com> wrote:

> Stuart,
>
> How did you get so smart? Is it the air in NPG?
>
> As for the 32->64 bt conversion, I cannot believe how llong this is taking.
> I keep thinking that I'm almost done, but then another insect bites me.
> Eventually I will bite baack all those insects, and when I'm done I will
> post the new files on my web site, so that no one else has to suffer this
> crap.
>
> On Thu, Dec 23, 2021 at 9:52 PM Stuart McLachlan <stuart at lexacorp.com.pg>
> wrote:
>
> > Depends on the organisation and the security requirements. :)
> >
> > If they have their own FEs and they are .accdb then it doesn't matter.
> > One size fits alll.
> >
> > If you want users to have accde, then you either upgrade everyone (which
> > may be costly if
> > you have old workstations and old versions of Office) or you have two
> > compiled versions.
> >
> > I've got clients in both scenarios, but as old machines are replaced and
> > office versions are
> > upgraded, they generally evolve to all 64 bit.
> >
> > (The only proviso is if you are using any 32bit extrenal liraries of
> > add-ons, you have to stick
> > with 32bit Access).
> >
> >
> >
> > On 23 Dec 2021 at 16:59, Rocky Smolin wrote:
> >
> > > What would your recommendation be in an environment with both 32 and
> > > 64 bit Office installed? Upgrade everyone to 64 bit?  Or have two
> > > versions of the app?
> > >
> > > r
> > >
> > > On Thu, Dec 23, 2021 at 2:10 PM Gustav Brock via AccessD <
> > > accessd at databaseadvisors.com> wrote:
> > >
> > > > Hi James
> > > >
> > > > 32-bit will probably exist as long Windows 10 is supported. Until
> > > > now, however, Windows 11 seems only to exist as 64-bit.
> > > >
> > > > But, as all new machines default to 64-bit Windows 10/11, there is
> > > > no reason to postpone the conversion of your database to 64-bit. If
> > > > you don?t use fancy 32-bit-only ActiveX controls, most likely, it
> > > > will be no-brainer.
> > > >
> > > > /gustav
> > > >
> > > > Fra: James Charlton<mailto:James at charltonweeks.com>
> > > > Sendt: 23. december 2021 23:04
> > > > Til: Access Developers discussion and problem solving<mailto:
> > > > accessd at databaseadvisors.com>
> > > > Emne: [AccessD] Converting to 64 Bit
> > > >
> > > > My partner is convinced that sooner or later Microsoft Office will
> > > > be exclusively 64 bit and therefore, sooner or later, our Access mdb
> > > > needs to be converted.  I spoke with Rocky who expressed disbelief
> > > > in that assessment.  What say you all? jc
> > > >
> > > > James Charlton
> > > > Charlton Weeks LLP
> > > > 1031 W Ave M14, Suite A
> > > > Palmdale, CA 93551
> > > > 661-265-0969
> > > > --
> > > > 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
> >
> >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
>
>
> --
> Arthur
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
Paul Rodgers BA (Hons) | solo Cape Horner |  paul4pr at gmail.com | +44 (0)78
6699 6377 | Google Local Guide
Bene agere et laetari. (To do good cheerfully.)

From pcs.accessd at gmail.com  Fri Dec 24 16:20:21 2021
From: pcs.accessd at gmail.com (Borge Hansen)
Date: Sat, 25 Dec 2021 08:20:21 +1000
Subject: [AccessD] OT: Merry Christmas
In-Reply-To: <AS8PR10MB43601D91AB1416BDE186985BCA7F9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
References: <HE1PR10MB0427ECCFBEE8DA866AB0FA6ECABB0@HE1PR10MB0427.EURPRD10.PROD.OUTLOOK.COM>
 <HE1PR10MB1692C7CFD1F4DEF39460BC7CCADD0@HE1PR10MB1692.EURPRD10.PROD.OUTLOOK.COM>
 <AS8PR10MB43601D91AB1416BDE186985BCA7F9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
Message-ID: <CAF+SPM-EJ1XoAm-wrwAfa8WRYXM2+Ygb6crs2QA0h192jBc=Mw@mail.gmail.com>

A merry Christmas and the very best wishes for a happy and fulfilling New
Year
/borge
from Gold Coast Australia
Xmas Day 8:20AM - partly cloudy and 26 degree Celsius in the shade

On Fri, 24 Dec 2021 at 10:58 pm, Gustav Brock via AccessD <
accessd at databaseadvisors.com> wrote:

> Hi all, including the faithful lurkers
>
> Last year was strange, but this year the vaccines are out. Still, no one
> can feel completely safe, indeed not the anti-vaccers, which I will never
> learn to understand.
>
> I hope you take your precautions to stay safe, and that you will enjoy a
> merry Christmas and a happy New Year!
> Gustav
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From stuart at lexacorp.com.pg  Fri Dec 24 17:53:01 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Sat, 25 Dec 2021 09:53:01 +1000
Subject: [AccessD] OT: Merry Christmas
In-Reply-To: <CAKvidAsvrg_cWKZ93Ho87qAti3bSq202+bE=W=0ZibQXPPjuqQ@mail.gmail.com>
References: <HE1PR10MB0427ECCFBEE8DA866AB0FA6ECABB0@HE1PR10MB0427.EURPRD10.PROD.OUTLOOK.COM>,
 <SYBP282MB0475E4237F9CAFB1BBEE8E52FF7F9@SYBP282MB0475.AUSP282.PROD.OUTLOOK.COM>,
 <CAKvidAsvrg_cWKZ93Ho87qAti3bSq202+bE=W=0ZibQXPPjuqQ@mail.gmail.com>
Message-ID: <61C65D5D.617.D308F4A@stuart.lexacorp.com.pg>

Merry Christmas to all from tropical Port Moresby!

The sun is shining, there's a light breeze and  an expected high of around 30?C / 86?F
I'm sitting in just a pair of shorts on my boat monitoring the radio for SAR watch while 
people head off for a day fishing or swimming and lounging on the coral sand beach of one 
of the local islands.  

We'll possibly take the SAR  boat out for a run around the islands later today  :)

-- 
Stuart


On 24 Dec 2021 at 8:18, jack drawbridge wrote:

> Merry Christmas to all from Canada. White with freezing rain in the
> forecast here. Let's hope 2022 will be a major improvement and more
> normal than 2020 and 2021. Stay healthy!
> 
> jack
> 
> 


From fuller.artful at gmail.com  Fri Dec 24 18:44:04 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Fri, 24 Dec 2021 19:44:04 -0500
Subject: [AccessD] Converting to 64 Bit
In-Reply-To: <CAKoNfVvQ56U+QG5sSDBOsMbHD28GqrApmPG0_8VQc+6eJq+4TA@mail.gmail.com>
References: <BYAPR05MB49834B7258AD573E6694E663AB7E9@BYAPR05MB4983.namprd05.prod.outlook.com>
 <AS8PR10MB43603B0C81A02F4F8D124DBBCA7E9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
 <CAEcmsdBFfcTHG2pNTM9wNxh3E4_vMojHy6PqqKa_CKyfgoWQzQ@mail.gmail.com>
 <61C535F3.1923.8AE9737@stuart.lexacorp.com.pg>
 <CAEPJO1jq+szsRP1uVqGVxCCUXqfDnrEczCCpQKL2ZfezYG+Vjg@mail.gmail.com>
 <CAKoNfVvQ56U+QG5sSDBOsMbHD28GqrApmPG0_8VQc+6eJq+4TA@mail.gmail.com>
Message-ID: <CAEPJO1jgb_TTZ+aB+wp+wAQz=USUH=7=s8+v38dF-5mxNQTj_A@mail.gmail.com>

Wow someone else on this list studied Latin. Must be a reflection of our
age. Nobody studies Latin nowadays, but those few of us who did can always
remember it. Silly lttle rhymes: ubi ibi hic hac hoc.  am 74 years old and
still remember that. Memory is a strange thig.

On Fri, Dec 24, 2021 at 4:50 PM paul <paulrster at gmail.com> wrote:

> Wishing you a great Christmas, Arthur. Hope it's all going really well for
> you.
> And hoping for a really good New Year's eve for you, leading into an
> excellent year.
>
> Best of best Christmas wishes
>
> Paul
>
>
>
>
>
> On Fri, 24 Dec 2021 at 17:15, Arthur Fuller <fuller.artful at gmail.com>
> wrote:
>
> > Stuart,
> >
> > How did you get so smart? Is it the air in NPG?
> >
> > As for the 32->64 bt conversion, I cannot believe how llong this is
> taking.
> > I keep thinking that I'm almost done, but then another insect bites me.
> > Eventually I will bite baack all those insects, and when I'm done I will
> > post the new files on my web site, so that no one else has to suffer this
> > crap.
> >
> > On Thu, Dec 23, 2021 at 9:52 PM Stuart McLachlan <stuart at lexacorp.com.pg
> >
> > wrote:
> >
> > > Depends on the organisation and the security requirements. :)
> > >
> > > If they have their own FEs and they are .accdb then it doesn't matter.
> > > One size fits alll.
> > >
> > > If you want users to have accde, then you either upgrade everyone
> (which
> > > may be costly if
> > > you have old workstations and old versions of Office) or you have two
> > > compiled versions.
> > >
> > > I've got clients in both scenarios, but as old machines are replaced
> and
> > > office versions are
> > > upgraded, they generally evolve to all 64 bit.
> > >
> > > (The only proviso is if you are using any 32bit extrenal liraries of
> > > add-ons, you have to stick
> > > with 32bit Access).
> > >
> > >
> > >
> > > On 23 Dec 2021 at 16:59, Rocky Smolin wrote:
> > >
> > > > What would your recommendation be in an environment with both 32 and
> > > > 64 bit Office installed? Upgrade everyone to 64 bit?  Or have two
> > > > versions of the app?
> > > >
> > > > r
> > > >
> > > > On Thu, Dec 23, 2021 at 2:10 PM Gustav Brock via AccessD <
> > > > accessd at databaseadvisors.com> wrote:
> > > >
> > > > > Hi James
> > > > >
> > > > > 32-bit will probably exist as long Windows 10 is supported. Until
> > > > > now, however, Windows 11 seems only to exist as 64-bit.
> > > > >
> > > > > But, as all new machines default to 64-bit Windows 10/11, there is
> > > > > no reason to postpone the conversion of your database to 64-bit. If
> > > > > you don?t use fancy 32-bit-only ActiveX controls, most likely, it
> > > > > will be no-brainer.
> > > > >
> > > > > /gustav
> > > > >
> > > > > Fra: James Charlton<mailto:James at charltonweeks.com>
> > > > > Sendt: 23. december 2021 23:04
> > > > > Til: Access Developers discussion and problem solving<mailto:
> > > > > accessd at databaseadvisors.com>
> > > > > Emne: [AccessD] Converting to 64 Bit
> > > > >
> > > > > My partner is convinced that sooner or later Microsoft Office will
> > > > > be exclusively 64 bit and therefore, sooner or later, our Access
> mdb
> > > > > needs to be converted.  I spoke with Rocky who expressed disbelief
> > > > > in that assessment.  What say you all? jc
> > > > >
> > > > > James Charlton
> > > > > Charlton Weeks LLP
> > > > > 1031 W Ave M14, Suite A
> > > > > Palmdale, CA 93551
> > > > > 661-265-0969
> > > > > --
> > > > > 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
> > >
> > >
> > > --
> > > AccessD mailing list
> > > AccessD at databaseadvisors.com
> > > https://databaseadvisors.com/mailman/listinfo/accessd
> > > Website: http://www.databaseadvisors.com
> > >
> >
> >
> > --
> > Arthur
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
>
>
> --
> Paul Rodgers BA (Hons) | solo Cape Horner |  paul4pr at gmail.com | +44 (0)78
> 6699 6377 | Google Local Guide
> Bene agere et laetari. (To do good cheerfully.)
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
Arthur

From stuart at lexacorp.com.pg  Fri Dec 24 19:09:23 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Sat, 25 Dec 2021 11:09:23 +1000
Subject: [AccessD] Converting to 64 Bit
In-Reply-To: <CAEPJO1jgb_TTZ+aB+wp+wAQz=USUH=7=s8+v38dF-5mxNQTj_A@mail.gmail.com>
References: <BYAPR05MB49834B7258AD573E6694E663AB7E9@BYAPR05MB4983.namprd05.prod.outlook.com>,
 <CAKoNfVvQ56U+QG5sSDBOsMbHD28GqrApmPG0_8VQc+6eJq+4TA@mail.gmail.com>,
 <CAEPJO1jgb_TTZ+aB+wp+wAQz=USUH=7=s8+v38dF-5mxNQTj_A@mail.gmail.com>
Message-ID: <61C66F43.257.D76770B@stuart.lexacorp.com.pg>

On 24 Dec 2021 at 19:44, Arthur Fuller wrote:

> Wow someone else on this list studied Latin. Must be a reflection of
> our age. Nobody studies Latin nowadays, but those few of us who did
> can always remember it. Silly lttle rhymes: ubi ibi hic hac hoc.  am
> 74 years old and still remember that. Memory is a strange thig.

SInce it's the silly season (and still Friday in some places), I guess we're allowed to go 
off-topic a bit :)

I still remember:
amo, amas, amat, amamus,, amatis, amant.

And then there was 
Caesar adsum iam forte
Brutus aderat
Caesar sic in omnibus
Brutus sic in at

:)



From fuller.artful at gmail.com  Sun Dec 26 17:25:03 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Sun, 26 Dec 2021 18:25:03 -0500
Subject: [AccessD] I'm drowning over here
In-Reply-To: <AS8PR10MB436024E1641B6F12A58F7AA3CA7E9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
References: <CAEPJO1jiFgNdfAED=j7gOZwYeZJmjickUsuUuA=xSe=PLWPefQ@mail.gmail.com>
 <AS8PR10MB436024E1641B6F12A58F7AA3CA7E9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
Message-ID: <CAEPJO1heq484xEKAt8Zx+s_HgNLhnazfEhJLowXCmgve9miSnA@mail.gmail.com>

Hi Gustav,

It's the Access 2000 Developer's Handbook.

On Thu, Dec 23, 2021 at 2:05 PM Gustav Brock via AccessD <
accessd at databaseadvisors.com> wrote:

> Hi Arthur
>
> What is adhCode, please?
>
> /gustav
>
>
> Fra: Arthur Fuller<mailto:fuller.artful at gmail.com>
> Sendt: 23. december 2021 19:06
> Til: Access Developers discussion and problem solving<mailto:
> accessd at databaseadvisors.com>
> Emne: [AccessD] I'm drowning over here
>
> Trying to solve the migration of adhCode to 64-bit and I am drowning. If
> there is anyone on this list who has solved these dilemmas, I humbly ask
> you to send me said files. I'm too old for this sort of aggravation. Back
> in the day, I relished this sort of challenge. No more. I a 74 years old.
> If there is anyone on this list who has been there and done that, I would
> love it if you would send me your updated files, with everything converted
> to 64 bit and also the conversions to LontPtr and LongLong, etc. I'm
> drowning over here and need a paddle! Pease.
>
> --
> Arthur
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
Arthur

From fuller.artful at gmail.com  Sun Dec 26 17:26:08 2021
From: fuller.artful at gmail.com (Arthur Fuller)
Date: Sun, 26 Dec 2021 18:26:08 -0500
Subject: [AccessD] Fwd: Merry Christmas
In-Reply-To: <CAEcmsdAJUKLbai+VWMqPeHP62ae1O5OujSX3kStJsJwuWNW2XQ@mail.gmail.com>
References: <CAEcmsdCGvs+AgogM+XcQcKqbVnZyJ4UvrxfgcWAT=1hSp=ShUg@mail.gmail.com>
 <CAEcmsdAJUKLbai+VWMqPeHP62ae1O5OujSX3kStJsJwuWNW2XQ@mail.gmail.com>
Message-ID: <CAEPJO1gnfp7Q+3w3EW0T6L+bbZKzJ7_UzLmHeW3rYtsft8XRHw@mail.gmail.com>

Same to you Rocky. All thebest in 2022.Rocky,

You are not alone in your rain. Here in Toronto we are supposed to have a
white Christmas but alacack and alas it is now +7 C. I am dressed in
sneakers and a light jacket. This is not how it is supposed to be. I guess
that the upside of global climate change is that pretty soon we shall be
growing avocados in Yellowknife, and all them Quebecois won't bot
ther visiting Florida any more. I guess we're in for a bunch of Miamipites
coming to Quebec.

On Fri, Dec 24, 2021 at 12:43 PM Rocky Smolin <rockysmolin2 at gmail.com>
wrote:

> Merry Christmas to all and a Happy New Year from Carlsbad in sunny Southern
> California where it's rainy and cold right now (so cold I have to wear
> socks!). Stay well this coming year.
>
> Best,
>
> Rocky
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
Arthur

From charlotte.foust at gmail.com  Sun Dec 26 17:33:39 2021
From: charlotte.foust at gmail.com (Charlotte Foust)
Date: Sun, 26 Dec 2021 15:33:39 -0800
Subject: [AccessD] I'm drowning over here
In-Reply-To: <CAEPJO1heq484xEKAt8Zx+s_HgNLhnazfEhJLowXCmgve9miSnA@mail.gmail.com>
References: <CAEPJO1jiFgNdfAED=j7gOZwYeZJmjickUsuUuA=xSe=PLWPefQ@mail.gmail.com>
 <AS8PR10MB436024E1641B6F12A58F7AA3CA7E9@AS8PR10MB4360.EURPRD10.PROD.OUTLOOK.COM>
 <CAEPJO1heq484xEKAt8Zx+s_HgNLhnazfEhJLowXCmgve9miSnA@mail.gmail.com>
Message-ID: <CAH+Met-p0pge2S8ucV_oO2Zb43tOc5QZ_K-rVKir6ZUDxWNAdw@mail.gmail.com>

Arthur,
The code in that version is out of date.  Access acquired out of the box
functionality that replaced many of the routines from that version.  It was
great code in its day, but a lot of it is unnecessary in current versions
of Access.  In other words, you would be better off just fixing the parts
of your code that breaks rather than trying to update a horse and buggy.

Charlotte Foust
(916) 206-4336


On Sun, Dec 26, 2021 at 3:25 PM Arthur Fuller <fuller.artful at gmail.com>
wrote:

> Hi Gustav,
>
> It's the Access 2000 Developer's Handbook.
>
> On Thu, Dec 23, 2021 at 2:05 PM Gustav Brock via AccessD <
> accessd at databaseadvisors.com> wrote:
>
> > Hi Arthur
> >
> > What is adhCode, please?
> >
> > /gustav
> >
> >
> > Fra: Arthur Fuller<mailto:fuller.artful at gmail.com>
> > Sendt: 23. december 2021 19:06
> > Til: Access Developers discussion and problem solving<mailto:
> > accessd at databaseadvisors.com>
> > Emne: [AccessD] I'm drowning over here
> >
> > Trying to solve the migration of adhCode to 64-bit and I am drowning. If
> > there is anyone on this list who has solved these dilemmas, I humbly ask
> > you to send me said files. I'm too old for this sort of aggravation. Back
> > in the day, I relished this sort of challenge. No more. I a 74 years old.
> > If there is anyone on this list who has been there and done that, I would
> > love it if you would send me your updated files, with everything
> converted
> > to 64 bit and also the conversions to LontPtr and LongLong, etc. I'm
> > drowning over here and need a paddle! Pease.
> >
> > --
> > Arthur
> >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > https://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
> >
>
>
> --
> Arthur
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From newsgrps at dalyn.co.nz  Sun Dec 26 19:31:54 2021
From: newsgrps at dalyn.co.nz (David Emerson)
Date: Mon, 27 Dec 2021 14:31:54 +1300
Subject: [AccessD] Updating SQL Connections
Message-ID: <000001d7fac1$89c3c660$9d4b5320$@dalyn.co.nz>

Hi Listers,

I hope you are having good holidays.

Has anyone come across the problem where you want to be able to change SQL Connection strings on distributed databases but don?t know what the string is?  Here is the situation:

A database application is sold to a client.  It has an Access FE and an SQL BE.  I want to be able to link to the SQL BE in code without having to hard code or set up the connection strings before giving the application the client.  The idea is that the connection string information can be stored in a place separate from the actual SQL database, in a place where the client can enter the details, but at the same time is safe from being discovered.

This excludes saving the connection string information in the SQL Database because the Access FE doesn?t have the connection details to be able to connect to the SQL database to get the connection string details ?

One idea is to store the information in a text file (encrypted of course) that the Access program can open first and check if the details have been updated.  If not then the Access program asks for the details, saves them to the file, then the file is used to get the connection string details for connecting the Access FE to the SQL backend.

Can anyone think of a better way of doing this, or any problems with this approach?

Regards

David Emerson
Dalyn Software Ltd
Wellington, New Zealand







From stuart at lexacorp.com.pg  Sun Dec 26 21:59:52 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Mon, 27 Dec 2021 13:59:52 +1000
Subject: [AccessD] Updating SQL Connections
In-Reply-To: <000001d7fac1$89c3c660$9d4b5320$@dalyn.co.nz>
References: <000001d7fac1$89c3c660$9d4b5320$@dalyn.co.nz>
Message-ID: <61C93A38.27225.185F3DAA@stuart.lexacorp.com.pg>

WHy a seprate file?   Use a usysTable in the FE that stores the connection string and have 
an Autoexec macro that checks the connection so startup. If it's not valid, pop up a form to 
maintain the data in the usysTable.

On 27 Dec 2021 at 14:31, David Emerson wrote:

> Hi Listers,
> 
> I hope you are having good holidays.
> 
> Has anyone come across the problem where you want to be able to change
> SQL Connection strings on distributed databases but don?t know what
> the string is?  Here is the situation:
> 
> A database application is sold to a client.  It has an Access FE and
> an SQL BE.  I want to be able to link to the SQL BE in code without
> having to hard code or set up the connection strings before giving the
> application the client.  The idea is that the connection string
> information can be stored in a place separate from the actual SQL
> database, in a place where the client can enter the details, but at
> the same time is safe from being discovered.
> 
> This excludes saving the connection string information in the SQL
> Database because the Access FE doesn?t have the connection details
> to be able to connect to the SQL database to get the connection string
> details 
> 
> One idea is to store the information in a text file (encrypted of
> course) that the Access program can open first and check if the
> details have been updated.  If not then the Access program asks for
> the details, saves them to the file, then the file is used to get the
> connection string details for connecting the Access FE to the SQL
> backend.
> 
> Can anyone think of a better way of doing this, or any problems with
> this approach?
> 
> Regards
> 
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand
> 
> 
> 
> 
> 
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com



From newsgrps at dalyn.co.nz  Sun Dec 26 23:56:54 2021
From: newsgrps at dalyn.co.nz (David Emerson)
Date: Mon, 27 Dec 2021 18:56:54 +1300
Subject: [AccessD] Updating SQL Connections
In-Reply-To: <61C93A38.27225.185F3DAA@stuart.lexacorp.com.pg>
References: <000001d7fac1$89c3c660$9d4b5320$@dalyn.co.nz>
 <61C93A38.27225.185F3DAA@stuart.lexacorp.com.pg>
Message-ID: <000301d7fae6$8f5cba80$ae162f80$@dalyn.co.nz>

Thanks Stuart - that was the better way of doing it that I was looking for ?

-----Original Message-----
From: AccessD <accessd-bounces+newsgrps=dalyn.co.nz at databaseadvisors.com> On Behalf Of Stuart McLachlan
Sent: Monday, 27 December 2021 5:00 pm
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Updating SQL Connections

WHy a seprate file?   Use a usysTable in the FE that stores the connection string and have 
an Autoexec macro that checks the connection so startup. If it's not valid, pop up a form to maintain the data in the usysTable.

On 27 Dec 2021 at 14:31, David Emerson wrote:

> Hi Listers,
> 
> I hope you are having good holidays.
> 
> Has anyone come across the problem where you want to be able to change 
> SQL Connection strings on distributed databases but don?t know what 
> the string is?  Here is the situation:
> 
> A database application is sold to a client.  It has an Access FE and 
> an SQL BE.  I want to be able to link to the SQL BE in code without 
> having to hard code or set up the connection strings before giving the 
> application the client.  The idea is that the connection string 
> information can be stored in a place separate from the actual SQL 
> database, in a place where the client can enter the details, but at 
> the same time is safe from being discovered.
> 
> This excludes saving the connection string information in the SQL 
> Database because the Access FE doesn?t have the connection details to 
> be able to connect to the SQL database to get the connection string 
> details
> 
> One idea is to store the information in a text file (encrypted of
> course) that the Access program can open first and check if the 
> details have been updated.  If not then the Access program asks for 
> the details, saves them to the file, then the file is used to get the 
> connection string details for connecting the Access FE to the SQL 
> backend.
> 
> Can anyone think of a better way of doing this, or any problems with 
> this approach?
> 
> Regards
> 
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand
> 
> 
> 
> 
> 
> 
> --
> 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


From jimdettman at verizon.net  Mon Dec 27 06:13:53 2021
From: jimdettman at verizon.net (Jim Dettman)
Date: Mon, 27 Dec 2021 07:13:53 -0500
Subject: [AccessD] Updating SQL Connections
In-Reply-To: <000301d7fae6$8f5cba80$ae162f80$@dalyn.co.nz>
References: <000001d7fac1$89c3c660$9d4b5320$@dalyn.co.nz>
 <61C93A38.27225.185F3DAA@stuart.lexacorp.com.pg>
 <000301d7fae6$8f5cba80$ae162f80$@dalyn.co.nz>
Message-ID: <00fc01d7fb1b$377d8260$a6788720$@verizon.net>


 Can't be "safe from being discovered", but you'd want to encrypt it anyway.

Jim.

-----Original Message-----
From: AccessD On Behalf Of David Emerson
Sent: Monday, December 27, 2021 12:57 AM
To: 'Access Developers discussion and problem solving' <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Updating SQL Connections

Thanks Stuart - that was the better way of doing it that I was looking for ?

-----Original Message-----
From: AccessD <accessd-bounces+newsgrps=dalyn.co.nz at databaseadvisors.com> On Behalf Of Stuart McLachlan
Sent: Monday, 27 December 2021 5:00 pm
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Updating SQL Connections

WHy a seprate file?   Use a usysTable in the FE that stores the connection string and have 
an Autoexec macro that checks the connection so startup. If it's not valid, pop up a form to maintain the data in the usysTable.

On 27 Dec 2021 at 14:31, David Emerson wrote:

> Hi Listers,
> 
> I hope you are having good holidays.
> 
> Has anyone come across the problem where you want to be able to change 
> SQL Connection strings on distributed databases but don?t know what 
> the string is?  Here is the situation:
> 
> A database application is sold to a client.  It has an Access FE and 
> an SQL BE.  I want to be able to link to the SQL BE in code without 
> having to hard code or set up the connection strings before giving the 
> application the client.  The idea is that the connection string 
> information can be stored in a place separate from the actual SQL 
> database, in a place where the client can enter the details, but at 
> the same time is safe from being discovered.
> 
> This excludes saving the connection string information in the SQL 
> Database because the Access FE doesn?t have the connection details to 
> be able to connect to the SQL database to get the connection string 
> details
> 
> One idea is to store the information in a text file (encrypted of
> course) that the Access program can open first and check if the 
> details have been updated.  If not then the Access program asks for 
> the details, saves them to the file, then the file is used to get the 
> connection string details for connecting the Access FE to the SQL 
> backend.
> 
> Can anyone think of a better way of doing this, or any problems with 
> this approach?
> 
> Regards
> 
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand
> 
> 
> 
> 
> 
> 
> --
> 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

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


From stuart at lexacorp.com.pg  Mon Dec 27 14:57:38 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Tue, 28 Dec 2021 06:57:38 +1000
Subject: [AccessD] Updating SQL Connections
In-Reply-To: <00fc01d7fb1b$377d8260$a6788720$@verizon.net>
References: <000001d7fac1$89c3c660$9d4b5320$@dalyn.co.nz>,
 <000301d7fae6$8f5cba80$ae162f80$@dalyn.co.nz>,
 <00fc01d7fb1b$377d8260$a6788720$@verizon.net>
Message-ID: <61CA28C2.1676.1C03033C@stuart.lexacorp.com.pg>

Not a lot of benefit to storing it encrypted since the same details will be available in the 
properties of any connected table once set up. 

And if they used WIndows security "TrustedConnection="Yes" instead of 
username/password, there's nothing highly sensitive there anyway :)

I've got a few application where they can use one of several BE's and store  connection 
details in a system table for switching between them,


On 27 Dec 2021 at 7:13, Jim Dettman via AccessD wrote:

> 
>  Can't be "safe from being discovered", but you'd want to encrypt it
>  anyway.
> 
> Jim.
> 
> -----Original Message-----
> From: AccessD On Behalf Of David Emerson
> Sent: Monday, December 27, 2021 12:57 AM
> To: 'Access Developers discussion and problem solving'
> <accessd at databaseadvisors.com> Subject: Re: [AccessD] Updating SQL
> Connections
> 
> Thanks Stuart - that was the better way of doing it that I was looking
> for 
> 
> -----Original Message-----
> From: AccessD
> <accessd-bounces+newsgrps=dalyn.co.nz at databaseadvisors.com> On Behalf
> Of Stuart McLachlan Sent: Monday, 27 December 2021 5:00 pm To: Access
> Developers discussion and problem solving
> <accessd at databaseadvisors.com> Subject: Re: [AccessD] Updating SQL
> Connections
> 
> WHy a seprate file?   Use a usysTable in the FE that stores the
> connection string and have an Autoexec macro that checks the
> connection so startup. If it's not valid, pop up a form to maintain
> the data in the usysTable.
> 
> On 27 Dec 2021 at 14:31, David Emerson wrote:
> 
> > Hi Listers,
> > 
> > I hope you are having good holidays.
> > 
> > Has anyone come across the problem where you want to be able to
> > change SQL Connection strings on distributed databases but don?t
> > know what the string is?  Here is the situation:
> > 
> > A database application is sold to a client.  It has an Access FE and
> > an SQL BE.  I want to be able to link to the SQL BE in code without
> > having to hard code or set up the connection strings before giving
> > the application the client.  The idea is that the connection string
> > information can be stored in a place separate from the actual SQL
> > database, in a place where the client can enter the details, but at
> > the same time is safe from being discovered.
> > 
> > This excludes saving the connection string information in the SQL
> > Database because the Access FE doesn?t have the connection details
> > to be able to connect to the SQL database to get the connection
> > string details
> > 
> > One idea is to store the information in a text file (encrypted of
> > course) that the Access program can open first and check if the
> > details have been updated.  If not then the Access program asks for
> > the details, saves them to the file, then the file is used to get
> > the connection string details for connecting the Access FE to the
> > SQL backend.
> > 
> > Can anyone think of a better way of doing this, or any problems with
> > this approach?
> > 
> > Regards
> > 
> > David Emerson
> > Dalyn Software Ltd
> > Wellington, New Zealand
> > 
> > 
> > 
> > 
> > 
> > 
> > --
> > 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
> 
> -- 
> 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



From jimdettman at verizon.net  Mon Dec 27 15:54:17 2021
From: jimdettman at verizon.net (Jim Dettman)
Date: Mon, 27 Dec 2021 16:54:17 -0500
Subject: [AccessD] Updating SQL Connections
In-Reply-To: <61CA28C2.1676.1C03033C@stuart.lexacorp.com.pg>
References: <000001d7fac1$89c3c660$9d4b5320$@dalyn.co.nz>,
 <000301d7fae6$8f5cba80$ae162f80$@dalyn.co.nz>,
 <00fc01d7fb1b$377d8260$a6788720$@verizon.net>
 <61CA28C2.1676.1C03033C@stuart.lexacorp.com.pg>
Message-ID: <025e01d7fb6c$4c2175e0$e46461a0$@verizon.net>


 Guess it depends on how much you want to lock it down.

 I've seen apps that setup connections at startup, then flush everything at
exit just to hide things. 

Jim.

-----Original Message-----
From: AccessD On Behalf Of Stuart McLachlan
Sent: Monday, December 27, 2021 3:58 PM
To: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] Updating SQL Connections

Not a lot of benefit to storing it encrypted since the same details will be
available in the 
properties of any connected table once set up. 

And if they used WIndows security "TrustedConnection="Yes" instead of 
username/password, there's nothing highly sensitive there anyway :)

I've got a few application where they can use one of several BE's and store
connection 
details in a system table for switching between them,


On 27 Dec 2021 at 7:13, Jim Dettman via AccessD wrote:

> 
>  Can't be "safe from being discovered", but you'd want to encrypt it
>  anyway.
> 
> Jim.
> 
> -----Original Message-----
> From: AccessD On Behalf Of David Emerson
> Sent: Monday, December 27, 2021 12:57 AM
> To: 'Access Developers discussion and problem solving'
> <accessd at databaseadvisors.com> Subject: Re: [AccessD] Updating SQL
> Connections
> 
> Thanks Stuart - that was the better way of doing it that I was looking
> for 
> 
> -----Original Message-----
> From: AccessD
> <accessd-bounces+newsgrps=dalyn.co.nz at databaseadvisors.com> On Behalf
> Of Stuart McLachlan Sent: Monday, 27 December 2021 5:00 pm To: Access
> Developers discussion and problem solving
> <accessd at databaseadvisors.com> Subject: Re: [AccessD] Updating SQL
> Connections
> 
> WHy a seprate file?   Use a usysTable in the FE that stores the
> connection string and have an Autoexec macro that checks the
> connection so startup. If it's not valid, pop up a form to maintain
> the data in the usysTable.
> 
> On 27 Dec 2021 at 14:31, David Emerson wrote:
> 
> > Hi Listers,
> > 
> > I hope you are having good holidays.
> > 
> > Has anyone come across the problem where you want to be able to
> > change SQL Connection strings on distributed databases but don?t
> > know what the string is?  Here is the situation:
> > 
> > A database application is sold to a client.  It has an Access FE and
> > an SQL BE.  I want to be able to link to the SQL BE in code without
> > having to hard code or set up the connection strings before giving
> > the application the client.  The idea is that the connection string
> > information can be stored in a place separate from the actual SQL
> > database, in a place where the client can enter the details, but at
> > the same time is safe from being discovered.
> > 
> > This excludes saving the connection string information in the SQL
> > Database because the Access FE doesn?t have the connection details
> > to be able to connect to the SQL database to get the connection
> > string details
> > 
> > One idea is to store the information in a text file (encrypted of
> > course) that the Access program can open first and check if the
> > details have been updated.  If not then the Access program asks for
> > the details, saves them to the file, then the file is used to get
> > the connection string details for connecting the Access FE to the
> > SQL backend.
> > 
> > Can anyone think of a better way of doing this, or any problems with
> > this approach?
> > 
> > Regards
> > 
> > David Emerson
> > Dalyn Software Ltd
> > Wellington, New Zealand
> > 
> > 
> > 
> > 
> > 
> > 
> > --
> > 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
> 
> -- 
> 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


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


From wrwehler at gmail.com  Mon Dec 27 17:35:20 2021
From: wrwehler at gmail.com (Ryan W)
Date: Mon, 27 Dec 2021 17:35:20 -0600
Subject: [AccessD] Access 2021 accde (64 bit) incompatible with Access 2013
 64 bit
Message-ID: <CAFXiSd93OLdDsoEXUK9DpVhHZwvdxfnFfGzbceebeV3GgP=+RQ@mail.gmail.com>

We're upgrading to Office 2021, I made a small change to a form to fit
better with the new UI (the runtime ribbon is a bit taller for some reason)
in one of my forms which fixed the form issue for a user currently running
Access 2021.

However, users who are still on 2013 during this rollout are now getting
2467 coming out of a JIT class John Colby assisted with, and a ribbon
button that simply calls DoCmd.OpenForm "MyFormName" now errors out with a
vague message.

Literally nothing in the DB changed aside from the one form, a decompile,
compile then compact&repair and a recompile into an accde and distributed.

I've since remedied the update mechanism I use to split 2013 and 2021
accde's into different directories on the server for them to pull down and
use... but was curious if anyone had any clues?  I'm not moving across
bit-ness or any major changes, no function calls that are erroring out rely
on conversion to 64 bit (PtrSafe etc).

Shouldn't this front end still function under an older version granted I
haven't changed anything that should be a show stopper?

The form I changed isn't even the form that the errors on open reference
either....

The challenge in debugging now is that I do not have an active copy of
Access 2013 64 bit that allows for development. Only runtime environments
for 2013.

From charlotte.foust at gmail.com  Mon Dec 27 18:21:04 2021
From: charlotte.foust at gmail.com (Charlotte Foust)
Date: Mon, 27 Dec 2021 16:21:04 -0800
Subject: [AccessD] Access 2021 accde (64 bit) incompatible with Access
 2013 64 bit
In-Reply-To: <CAFXiSd93OLdDsoEXUK9DpVhHZwvdxfnFfGzbceebeV3GgP=+RQ@mail.gmail.com>
References: <CAFXiSd93OLdDsoEXUK9DpVhHZwvdxfnFfGzbceebeV3GgP=+RQ@mail.gmail.com>
Message-ID: <CAH+Met_VZC2rKp00yt+pWtS2cC-q3C9doRu492-W=mUGYTfPqQ@mail.gmail.com>

You have to use the compiler for the version or you get the kind of vague
errors you are seeing.  If you do not have an active version of 2013 to
compile the changed database with, it isn't going to work for 2013 users.

Charlotte Foust
(916) 206-4336


On Mon, Dec 27, 2021 at 3:35 PM Ryan W <wrwehler at gmail.com> wrote:

> We're upgrading to Office 2021, I made a small change to a form to fit
> better with the new UI (the runtime ribbon is a bit taller for some reason)
> in one of my forms which fixed the form issue for a user currently running
> Access 2021.
>
> However, users who are still on 2013 during this rollout are now getting
> 2467 coming out of a JIT class John Colby assisted with, and a ribbon
> button that simply calls DoCmd.OpenForm "MyFormName" now errors out with a
> vague message.
>
> Literally nothing in the DB changed aside from the one form, a decompile,
> compile then compact&repair and a recompile into an accde and distributed.
>
> I've since remedied the update mechanism I use to split 2013 and 2021
> accde's into different directories on the server for them to pull down and
> use... but was curious if anyone had any clues?  I'm not moving across
> bit-ness or any major changes, no function calls that are erroring out rely
> on conversion to 64 bit (PtrSafe etc).
>
> Shouldn't this front end still function under an older version granted I
> haven't changed anything that should be a show stopper?
>
> The form I changed isn't even the form that the errors on open reference
> either....
>
> The challenge in debugging now is that I do not have an active copy of
> Access 2013 64 bit that allows for development. Only runtime environments
> for 2013.
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From wrwehler at gmail.com  Mon Dec 27 18:38:35 2021
From: wrwehler at gmail.com (Ryan W)
Date: Mon, 27 Dec 2021 18:38:35 -0600
Subject: [AccessD] Access 2021 accde (64 bit) incompatible with Access
 2013 64 bit
In-Reply-To: <CAH+Met_VZC2rKp00yt+pWtS2cC-q3C9doRu492-W=mUGYTfPqQ@mail.gmail.com>
References: <CAH+Met_VZC2rKp00yt+pWtS2cC-q3C9doRu492-W=mUGYTfPqQ@mail.gmail.com>
Message-ID: <C2DA51ED-38E7-47A0-9074-ED0D22F43BED@gmail.com>

Really? Considering the code base and feature set has mostly remained unchanged in both my file and Access in general that is frustrating as heck. 

Do you have any official documentation to back this up? I tried to find anything saying so before I emailed the group. 
I know there was a big change between mde and accde and then ADP projects going bye bye. 

Sent from my iPhone

> On Dec 27, 2021, at 6:21 PM, Charlotte Foust <charlotte.foust at gmail.com> wrote:
> 
> ?You have to use the compiler for the version or you get the kind of vague
> errors you are seeing.  If you do not have an active version of 2013 to
> compile the changed database with, it isn't going to work for 2013 users.
> 
> Charlotte Foust
> (916) 206-4336
> 
> 
>> On Mon, Dec 27, 2021 at 3:35 PM Ryan W <wrwehler at gmail.com> wrote:
>> 
>> We're upgrading to Office 2021, I made a small change to a form to fit
>> better with the new UI (the runtime ribbon is a bit taller for some reason)
>> in one of my forms which fixed the form issue for a user currently running
>> Access 2021.
>> 
>> However, users who are still on 2013 during this rollout are now getting
>> 2467 coming out of a JIT class John Colby assisted with, and a ribbon
>> button that simply calls DoCmd.OpenForm "MyFormName" now errors out with a
>> vague message.
>> 
>> Literally nothing in the DB changed aside from the one form, a decompile,
>> compile then compact&repair and a recompile into an accde and distributed.
>> 
>> I've since remedied the update mechanism I use to split 2013 and 2021
>> accde's into different directories on the server for them to pull down and
>> use... but was curious if anyone had any clues?  I'm not moving across
>> bit-ness or any major changes, no function calls that are erroring out rely
>> on conversion to 64 bit (PtrSafe etc).
>> 
>> Shouldn't this front end still function under an older version granted I
>> haven't changed anything that should be a show stopper?
>> 
>> The form I changed isn't even the form that the errors on open reference
>> either....
>> 
>> The challenge in debugging now is that I do not have an active copy of
>> Access 2013 64 bit that allows for development. Only runtime environments
>> for 2013.
>> --
>> 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

From jwcolby at gmail.com  Mon Dec 27 20:01:59 2021
From: jwcolby at gmail.com (John Colby)
Date: Mon, 27 Dec 2021 21:01:59 -0500
Subject: [AccessD] Access 2021 accde (64 bit) incompatible with Access
 2013 64 bit
In-Reply-To: <CAFXiSd93OLdDsoEXUK9DpVhHZwvdxfnFfGzbceebeV3GgP=+RQ@mail.gmail.com>
References: <CAFXiSd93OLdDsoEXUK9DpVhHZwvdxfnFfGzbceebeV3GgP=+RQ@mail.gmail.com>
Message-ID: <CAA_iUE8_pjWi_74tOQPptE_BOFMgp1uDnj0N7Kw=aDyMO91B3g@mail.gmail.com>

can you do a decompile / compile under the Office 2021 32 bit compiler?
Send the resulting file to those clients still on 2013.  I think the
"Bitness" of the compiler is exactly the problem.  A 64 bit compiler is
going to make fundamental changes to pointer lengths etc.
You might have to run a virtual machine where you install a 32 bit version
of Office 2021 so you can do the compile under the 32 bit compiler.



On Mon, Dec 27, 2021 at 6:35 PM Ryan W <wrwehler at gmail.com> wrote:

> We're upgrading to Office 2021, I made a small change to a form to fit
> better with the new UI (the runtime ribbon is a bit taller for some reason)
> in one of my forms which fixed the form issue for a user currently running
> Access 2021.
>
> However, users who are still on 2013 during this rollout are now getting
> 2467 coming out of a JIT class John Colby assisted with, and a ribbon
> button that simply calls DoCmd.OpenForm "MyFormName" now errors out with a
> vague message.
>
> Literally nothing in the DB changed aside from the one form, a decompile,
> compile then compact&repair and a recompile into an accde and distributed.
>
> I've since remedied the update mechanism I use to split 2013 and 2021
> accde's into different directories on the server for them to pull down and
> use... but was curious if anyone had any clues?  I'm not moving across
> bit-ness or any major changes, no function calls that are erroring out rely
> on conversion to 64 bit (PtrSafe etc).
>
> Shouldn't this front end still function under an older version granted I
> haven't changed anything that should be a show stopper?
>
> The form I changed isn't even the form that the errors on open reference
> either....
>
> The challenge in debugging now is that I do not have an active copy of
> Access 2013 64 bit that allows for development. Only runtime environments
> for 2013.
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
John W. Colby
Colby Consulting

From jwcolby at gmail.com  Mon Dec 27 20:06:20 2021
From: jwcolby at gmail.com (John Colby)
Date: Mon, 27 Dec 2021 21:06:20 -0500
Subject: [AccessD] Updating SQL Connections
In-Reply-To: <000001d7fac1$89c3c660$9d4b5320$@dalyn.co.nz>
References: <000001d7fac1$89c3c660$9d4b5320$@dalyn.co.nz>
Message-ID: <CAA_iUE90nL+CzDVLKMip6UpqmruZ=wXtAyqbAWw_CU8=NmBp1A@mail.gmail.com>

usys tables work. I also use database properties which are pretty obscure
for non-developers.  You and I can read / write to them but non-developers
don't even realize they are there.

On Sun, Dec 26, 2021 at 8:32 PM David Emerson <newsgrps at dalyn.co.nz> wrote:

> Hi Listers,
>
> I hope you are having good holidays.
>
> Has anyone come across the problem where you want to be able to change SQL
> Connection strings on distributed databases but don?t know what the string
> is?  Here is the situation:
>
> A database application is sold to a client.  It has an Access FE and an
> SQL BE.  I want to be able to link to the SQL BE in code without having to
> hard code or set up the connection strings before giving the application
> the client.  The idea is that the connection string information can be
> stored in a place separate from the actual SQL database, in a place where
> the client can enter the details, but at the same time is safe from being
> discovered.
>
> This excludes saving the connection string information in the SQL Database
> because the Access FE doesn?t have the connection details to be able to
> connect to the SQL database to get the connection string details ?
>
> One idea is to store the information in a text file (encrypted of course)
> that the Access program can open first and check if the details have been
> updated.  If not then the Access program asks for the details, saves them
> to the file, then the file is used to get the connection string details for
> connecting the Access FE to the SQL backend.
>
> Can anyone think of a better way of doing this, or any problems with this
> approach?
>
> Regards
>
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand
>
>
>
>
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


-- 
John W. Colby
Colby Consulting

From wrwehler at gmail.com  Mon Dec 27 20:15:47 2021
From: wrwehler at gmail.com (Ryan W)
Date: Mon, 27 Dec 2021 20:15:47 -0600
Subject: [AccessD] Access 2021 accde (64 bit) incompatible with Access
 2013 64 bit
In-Reply-To: <CAA_iUE8_pjWi_74tOQPptE_BOFMgp1uDnj0N7Kw=aDyMO91B3g@mail.gmail.com>
References: <CAA_iUE8_pjWi_74tOQPptE_BOFMgp1uDnj0N7Kw=aDyMO91B3g@mail.gmail.com>
Message-ID: <07299D5E-8B7B-48C0-BF54-9142020111DE@gmail.com>

I?m not changing bitness. Last week I was using 2013 64. This week 2021 64. 

None of my desktop clients use 32 bit access anymore. 

Unfortunately the accde file saved under 2021 doesn?t work on 2013 with the same bitness. It throws some errors on startup they weren?t there with the 2013 saved accde from last week before I upgraded. 

Sent from my iPhone

> On Dec 27, 2021, at 8:02 PM, John Colby <jwcolby at gmail.com> wrote:
> 
> ?can you do a decompile / compile under the Office 2021 32 bit compiler?
> Send the resulting file to those clients still on 2013.  I think the
> "Bitness" of the compiler is exactly the problem.  A 64 bit compiler is
> going to make fundamental changes to pointer lengths etc.
> You might have to run a virtual machine where you install a 32 bit version
> of Office 2021 so you can do the compile under the 32 bit compiler.
> 
> 
> 
>> On Mon, Dec 27, 2021 at 6:35 PM Ryan W <wrwehler at gmail.com> wrote:
>> 
>> We're upgrading to Office 2021, I made a small change to a form to fit
>> better with the new UI (the runtime ribbon is a bit taller for some reason)
>> in one of my forms which fixed the form issue for a user currently running
>> Access 2021.
>> 
>> However, users who are still on 2013 during this rollout are now getting
>> 2467 coming out of a JIT class John Colby assisted with, and a ribbon
>> button that simply calls DoCmd.OpenForm "MyFormName" now errors out with a
>> vague message.
>> 
>> Literally nothing in the DB changed aside from the one form, a decompile,
>> compile then compact&repair and a recompile into an accde and distributed.
>> 
>> I've since remedied the update mechanism I use to split 2013 and 2021
>> accde's into different directories on the server for them to pull down and
>> use... but was curious if anyone had any clues?  I'm not moving across
>> bit-ness or any major changes, no function calls that are erroring out rely
>> on conversion to 64 bit (PtrSafe etc).
>> 
>> Shouldn't this front end still function under an older version granted I
>> haven't changed anything that should be a show stopper?
>> 
>> The form I changed isn't even the form that the errors on open reference
>> either....
>> 
>> The challenge in debugging now is that I do not have an active copy of
>> Access 2013 64 bit that allows for development. Only runtime environments
>> for 2013.
>> --
>> AccessD mailing list
>> AccessD at databaseadvisors.com
>> https://databaseadvisors.com/mailman/listinfo/accessd
>> Website: http://www.databaseadvisors.com
>> 
> 
> 
> -- 
> John W. Colby
> Colby Consulting
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com

From stuart at lexacorp.com.pg  Mon Dec 27 21:27:23 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Tue, 28 Dec 2021 13:27:23 +1000
Subject: [AccessD] Access 2021 accde (64 bit) incompatible with Access
 2013 64 bit
In-Reply-To: <07299D5E-8B7B-48C0-BF54-9142020111DE@gmail.com>
References: <CAA_iUE8_pjWi_74tOQPptE_BOFMgp1uDnj0N7Kw=aDyMO91B3g@mail.gmail.com>,
 <07299D5E-8B7B-48C0-BF54-9142020111DE@gmail.com>
Message-ID: <61CA841B.12303.1D67D55D@stuart.lexacorp.com.pg>

It's ever been thus.

Opening an accee with  that's been compiled with a more recent version than you are 
using.opening it with is frequently problematic.

You need to compile on the lowest version that will be using it.

https://support.microsoft.com/en-us/office/deploy-an-access-application-7bb4f2ba-30ee-458
c-a673-102dc34bf14fhttps://support.microsoft.com/en-us/office/deploy-an-access-applicatio
n-7bb4f2ba-30ee-458c-a673-102dc34bf14f

Important???Users can't open a compiled binary file by using an earlier version of 
Access than the version in which it was compiled if the earlier version doesn?t 
support a feature added in the later version. To resolve this issue, compile the 
binary file in the Access version your users have installed.



On 27 Dec 2021 at 20:15, Ryan W wrote:

> I?m not changing bitness. Last week I was using 2013 64. This week
> 2021 64. 
> 
> None of my desktop clients use 32 bit access anymore. 
> 
> Unfortunately the accde file saved under 2021 doesn?t work on 2013
> with the same bitness. It throws some errors on startup they weren?t
> there with the 2013 saved accde from last week before I upgraded. 
> 
> Sent from my iPhone
> 
> > On Dec 27, 2021, at 8:02 PM, John Colby <jwcolby at gmail.com> wrote:
> > 
> > can you do a decompile / compile under the Office 2021 32 bit
> > compiler? Send the resulting file to those clients still on 2013.  I
> > think the "Bitness" of the compiler is exactly the problem.  A 64
> > bit compiler is going to make fundamental changes to pointer lengths
> > etc. You might have to run a virtual machine where you install a 32
> > bit version of Office 2021 so you can do the compile under the 32
> > bit compiler.
> > 
> > 
> > 
> >> On Mon, Dec 27, 2021 at 6:35 PM Ryan W <wrwehler at gmail.com> wrote:
> >> 
> >> We're upgrading to Office 2021, I made a small change to a form to
> >> fit better with the new UI (the runtime ribbon is a bit taller for
> >> some reason) in one of my forms which fixed the form issue for a
> >> user currently running Access 2021.
> >> 
> >> However, users who are still on 2013 during this rollout are now
> >> getting 2467 coming out of a JIT class John Colby assisted with,
> >> and a ribbon button that simply calls DoCmd.OpenForm "MyFormName"
> >> now errors out with a vague message.
> >> 
> >> Literally nothing in the DB changed aside from the one form, a
> >> decompile, compile then compact&repair and a recompile into an
> >> accde and distributed.
> >> 
> >> I've since remedied the update mechanism I use to split 2013 and
> >> 2021 accde's into different directories on the server for them to
> >> pull down and use... but was curious if anyone had any clues?  I'm
> >> not moving across bit-ness or any major changes, no function calls
> >> that are erroring out rely on conversion to 64 bit (PtrSafe etc).
> >> 
> >> Shouldn't this front end still function under an older version
> >> granted I haven't changed anything that should be a show stopper?
> >> 
> >> The form I changed isn't even the form that the errors on open
> >> reference either....
> >> 
> >> The challenge in debugging now is that I do not have an active copy
> >> of Access 2013 64 bit that allows for development. Only runtime
> >> environments for 2013. -- AccessD mailing list
> >> AccessD at databaseadvisors.com
> >> https://databaseadvisors.com/mailman/listinfo/accessd Website:
> >> http://www.databaseadvisors.com
> >> 
> > 
> > 
> > -- 
> > John W. Colby
> > Colby Consulting
> > -- 
> > 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



From newsgrps at dalyn.co.nz  Tue Dec 28 00:39:58 2021
From: newsgrps at dalyn.co.nz (David Emerson)
Date: Tue, 28 Dec 2021 19:39:58 +1300
Subject: [AccessD] Updating SQL Connections
In-Reply-To: <CAA_iUE90nL+CzDVLKMip6UpqmruZ=wXtAyqbAWw_CU8=NmBp1A@mail.gmail.com>
References: <000001d7fac1$89c3c660$9d4b5320$@dalyn.co.nz>
 <CAA_iUE90nL+CzDVLKMip6UpqmruZ=wXtAyqbAWw_CU8=NmBp1A@mail.gmail.com>
Message-ID: <000601d7fbb5$bf8ead10$3eac0730$@dalyn.co.nz>

Thanks for the suggestion John.

-----Original Message-----
From: AccessD <accessd-bounces+newsgrps=dalyn.co.nz at databaseadvisors.com> On Behalf Of John Colby
Sent: Tuesday, 28 December 2021 3:06 pm
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Subject: Re: [AccessD] Updating SQL Connections

usys tables work. I also use database properties which are pretty obscure for non-developers.  You and I can read / write to them but non-developers don't even realize they are there.

On Sun, Dec 26, 2021 at 8:32 PM David Emerson <newsgrps at dalyn.co.nz> wrote:

> Hi Listers,
>
> I hope you are having good holidays.
>
> Has anyone come across the problem where you want to be able to change 
> SQL Connection strings on distributed databases but don?t know what 
> the string is?  Here is the situation:
>
> A database application is sold to a client.  It has an Access FE and 
> an SQL BE.  I want to be able to link to the SQL BE in code without 
> having to hard code or set up the connection strings before giving the 
> application the client.  The idea is that the connection string 
> information can be stored in a place separate from the actual SQL 
> database, in a place where the client can enter the details, but at 
> the same time is safe from being discovered.
>
> This excludes saving the connection string information in the SQL 
> Database because the Access FE doesn?t have the connection details to 
> be able to connect to the SQL database to get the connection string 
> details ?
>
> One idea is to store the information in a text file (encrypted of 
> course) that the Access program can open first and check if the 
> details have been updated.  If not then the Access program asks for 
> the details, saves them to the file, then the file is used to get the 
> connection string details for connecting the Access FE to the SQL backend.
>
> Can anyone think of a better way of doing this, or any problems with 
> this approach?
>
> Regards
>
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand
>
>
>
>
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>


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


From jimdettman at verizon.net  Tue Dec 28 03:45:08 2021
From: jimdettman at verizon.net (Jim Dettman)
Date: Tue, 28 Dec 2021 04:45:08 -0500
Subject: [AccessD] Access 2021 accde (64 bit) incompatible with Access
 2013 64 bit
In-Reply-To: <CAFXiSd93OLdDsoEXUK9DpVhHZwvdxfnFfGzbceebeV3GgP=+RQ@mail.gmail.com>
References: <CAFXiSd93OLdDsoEXUK9DpVhHZwvdxfnFfGzbceebeV3GgP=+RQ@mail.gmail.com>
Message-ID: <02a601d7fbcf$99c38a50$cd4a9ef0$@verizon.net>


 As Charlotte and Stuart noted, going backward is problematic.

 One thing I would check is the references.  Some will automatically update
to the latest version.   You compile and distribute, and now your earlier
users have a problem.   Usually though that will outright break the app.
However, with Access 2013 and up, a lot of things have changed internally
and it's now all the same "version" more or less because a lot more is
shared across versions.   That's why you can't mix bitness between versions
anymore with Office 2013 and up (i.e. you can't have Access 2013 32 bit, and
Access 2016 64 bit on the same machine).   It's also why from Access 2016
and up, you'll always get 16 as the version.

 And of course that's outside of all the features that get turned on and off
now based on your license/version, which easily could effect how the ribbon
behaves.

 As noted, always develop/compile in the lowest version that your users will
be using, and this a rule of thumb that has always been true with Access.

 I would setup a couple of VM's on the development machine and have 32 and
64 bit edition of Access 2013 installed in those.

 Jim.

-----Original Message-----
From: AccessD On Behalf Of Ryan W
Sent: Monday, December 27, 2021 6:35 PM
To: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>
Subject: [AccessD] Access 2021 accde (64 bit) incompatible with Access 2013
64 bit

We're upgrading to Office 2021, I made a small change to a form to fit
better with the new UI (the runtime ribbon is a bit taller for some reason)
in one of my forms which fixed the form issue for a user currently running
Access 2021.

However, users who are still on 2013 during this rollout are now getting
2467 coming out of a JIT class John Colby assisted with, and a ribbon
button that simply calls DoCmd.OpenForm "MyFormName" now errors out with a
vague message.

Literally nothing in the DB changed aside from the one form, a decompile,
compile then compact&repair and a recompile into an accde and distributed.

I've since remedied the update mechanism I use to split 2013 and 2021
accde's into different directories on the server for them to pull down and
use... but was curious if anyone had any clues?  I'm not moving across
bit-ness or any major changes, no function calls that are erroring out rely
on conversion to 64 bit (PtrSafe etc).

Shouldn't this front end still function under an older version granted I
haven't changed anything that should be a show stopper?

The form I changed isn't even the form that the errors on open reference
either....

The challenge in debugging now is that I do not have an active copy of
Access 2013 64 bit that allows for development. Only runtime environments
for 2013.
-- 
AccessD mailing list
AccessD at databaseadvisors.com
https://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com


From wrwehler at gmail.com  Tue Dec 28 08:05:32 2021
From: wrwehler at gmail.com (Ryan W)
Date: Tue, 28 Dec 2021 08:05:32 -0600
Subject: [AccessD] Office 2021 licensing (heads up)
Message-ID: <CAFXiSd9a-MywnmuHVd4gZS-GVOgAwZL4UHQ1DKaScQAuLtsD2A@mail.gmail.com>

Just in case any of you are looking to buy perpetual licenses, since their
licensing model changed and you buy the licenses from a CSP, they no longer
give you a KMS host key.

This is really going to pooch my rollout. I roll 5 new versions out at a
time and now I'll likely have to keep track of MAK activations instead of
just using KMS or ADDS activations.

Sell on-premises software through CSP - Partner Center | Microsoft Docs
<https://docs.microsoft.com/en-us/partner-center/csp-on-premises-software>

The licenses no longer show up in VLSC, instead they show up in your 365
administrator panel.

This is a really bizarre move.  I have machines that do not have routable
internet which will give me grief when trying to activate a MAK key.

From wrwehler at gmail.com  Tue Dec 28 08:15:25 2021
From: wrwehler at gmail.com (Ryan W)
Date: Tue, 28 Dec 2021 08:15:25 -0600
Subject: [AccessD] Access 2021 accde (64 bit) incompatible with Access
 2013 64 bit
In-Reply-To: <61CA841B.12303.1D67D55D@stuart.lexacorp.com.pg>
References: <CAA_iUE8_pjWi_74tOQPptE_BOFMgp1uDnj0N7Kw=aDyMO91B3g@mail.gmail.com>
 <07299D5E-8B7B-48C0-BF54-9142020111DE@gmail.com>
 <61CA841B.12303.1D67D55D@stuart.lexacorp.com.pg>
Message-ID: <CAFXiSd8eic=V6jsS+gQ5fG8zd4wWZh0bnxQrVz4_qO0tQBM5Fg@mail.gmail.com>

Okay fair enough. Your link does say that but Access has been so stale on
the development front for some time that the differences between 2013 and
2021 are minimal AT BEST.

I've installed Access 2013 64-bit on a VM and compiled it. I guess this
will have to work for now.



On Mon, Dec 27, 2021 at 9:27 PM Stuart McLachlan <stuart at lexacorp.com.pg>
wrote:

> It's ever been thus.
>
> Opening an accee with  that's been compiled with a more recent version
> than you are
> using.opening it with is frequently problematic.
>
> You need to compile on the lowest version that will be using it.
>
>
> https://support.microsoft.com/en-us/office/deploy-an-access-application-7bb4f2ba-30ee-458
>
> c-a673-102dc34bf14fhttps://support.microsoft.com/en-us/office/deploy-an-access-applicatio
> n-7bb4f2ba-30ee-458c-a673-102dc34bf14f
> <https://support.microsoft.com/en-us/office/deploy-an-access-application-7bb4f2ba-30ee-458c-a673-102dc34bf14fhttps://support.microsoft.com/en-us/office/deploy-an-access-application-7bb4f2ba-30ee-458c-a673-102dc34bf14f>
>
> Important   Users can't open a compiled binary file by using an earlier
> version of
> Access than the version in which it was compiled if the earlier version
> doesn?t
> support a feature added in the later version. To resolve this issue,
> compile the
> binary file in the Access version your users have installed.
>
>
>
> On 27 Dec 2021 at 20:15, Ryan W wrote:
>
> > I?m not changing bitness. Last week I was using 2013 64. This week
> > 2021 64.
> >
> > None of my desktop clients use 32 bit access anymore.
> >
> > Unfortunately the accde file saved under 2021 doesn?t work on 2013
> > with the same bitness. It throws some errors on startup they weren?t
> > there with the 2013 saved accde from last week before I upgraded.
> >
> > Sent from my iPhone
> >
> > > On Dec 27, 2021, at 8:02 PM, John Colby <jwcolby at gmail.com> wrote:
> > >
> > > can you do a decompile / compile under the Office 2021 32 bit
> > > compiler? Send the resulting file to those clients still on 2013.  I
> > > think the "Bitness" of the compiler is exactly the problem.  A 64
> > > bit compiler is going to make fundamental changes to pointer lengths
> > > etc. You might have to run a virtual machine where you install a 32
> > > bit version of Office 2021 so you can do the compile under the 32
> > > bit compiler.
> > >
> > >
> > >
> > >> On Mon, Dec 27, 2021 at 6:35 PM Ryan W <wrwehler at gmail.com> wrote:
> > >>
> > >> We're upgrading to Office 2021, I made a small change to a form to
> > >> fit better with the new UI (the runtime ribbon is a bit taller for
> > >> some reason) in one of my forms which fixed the form issue for a
> > >> user currently running Access 2021.
> > >>
> > >> However, users who are still on 2013 during this rollout are now
> > >> getting 2467 coming out of a JIT class John Colby assisted with,
> > >> and a ribbon button that simply calls DoCmd.OpenForm "MyFormName"
> > >> now errors out with a vague message.
> > >>
> > >> Literally nothing in the DB changed aside from the one form, a
> > >> decompile, compile then compact&repair and a recompile into an
> > >> accde and distributed.
> > >>
> > >> I've since remedied the update mechanism I use to split 2013 and
> > >> 2021 accde's into different directories on the server for them to
> > >> pull down and use... but was curious if anyone had any clues?  I'm
> > >> not moving across bit-ness or any major changes, no function calls
> > >> that are erroring out rely on conversion to 64 bit (PtrSafe etc).
> > >>
> > >> Shouldn't this front end still function under an older version
> > >> granted I haven't changed anything that should be a show stopper?
> > >>
> > >> The form I changed isn't even the form that the errors on open
> > >> reference either....
> > >>
> > >> The challenge in debugging now is that I do not have an active copy
> > >> of Access 2013 64 bit that allows for development. Only runtime
> > >> environments for 2013. -- AccessD mailing list
> > >> AccessD at databaseadvisors.com
> > >> https://databaseadvisors.com/mailman/listinfo/accessd Website:
> > >> http://www.databaseadvisors.com
> > >>
> > >
> > >
> > > --
> > > John W. Colby
> > > Colby Consulting
> > > --
> > > 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
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>

From stuart at lexacorp.com.pg  Tue Dec 28 18:12:49 2021
From: stuart at lexacorp.com.pg (Stuart McLachlan)
Date: Wed, 29 Dec 2021 10:12:49 +1000
Subject: [AccessD] Access 2021 accde (64 bit) incompatible with Access
 2013 64 bit
In-Reply-To: <CAFXiSd8eic=V6jsS+gQ5fG8zd4wWZh0bnxQrVz4_qO0tQBM5Fg@mail.gmail.com>
References: <CAA_iUE8_pjWi_74tOQPptE_BOFMgp1uDnj0N7Kw=aDyMO91B3g@mail.gmail.com>,
 <61CA841B.12303.1D67D55D@stuart.lexacorp.com.pg>,
 <CAFXiSd8eic=V6jsS+gQ5fG8zd4wWZh0bnxQrVz4_qO0tQBM5Fg@mail.gmail.com>
Message-ID: <61CBA801.12497.21DC1098@stuart.lexacorp.com.pg>

One major difference between 2013 and 2021 is the LargeNumber/BigInt data type 
introduced in 2016.


On 28 Dec 2021 at 8:15, Ryan W wrote:

> Okay fair enough. Your link does say that but Access has been so stale
> on the development front for some time that the differences between
> 2013 and 2021 are minimal AT BEST.
> 
> I've installed Access 2013 64-bit on a VM and compiled it. I guess
> this will have to work for now.
> 
> 
> 


From jwcolby at gmail.com  Tue Dec 28 18:27:15 2021
From: jwcolby at gmail.com (John Colby)
Date: Tue, 28 Dec 2021 19:27:15 -0500
Subject: [AccessD] Access 2021 accde (64 bit) incompatible with Access
 2013 64 bit
In-Reply-To: <CAFXiSd8eic=V6jsS+gQ5fG8zd4wWZh0bnxQrVz4_qO0tQBM5Fg@mail.gmail.com>
References: <CAA_iUE8_pjWi_74tOQPptE_BOFMgp1uDnj0N7Kw=aDyMO91B3g@mail.gmail.com>
 <07299D5E-8B7B-48C0-BF54-9142020111DE@gmail.com>
 <61CA841B.12303.1D67D55D@stuart.lexacorp.com.pg>
 <CAFXiSd8eic=V6jsS+gQ5fG8zd4wWZh0bnxQrVz4_qO0tQBM5Fg@mail.gmail.com>
Message-ID: <CAA_iUE9MC_vknpGLicjnw==FHZvZqafQjLg=9FXY4wqC9qC3Rw@mail.gmail.com>

Did that fix the problem?

On Tue, Dec 28, 2021 at 9:15 AM Ryan W <wrwehler at gmail.com> wrote:

> Okay fair enough. Your link does say that but Access has been so stale on
> the development front for some time that the differences between 2013 and
> 2021 are minimal AT BEST.
>
> I've installed Access 2013 64-bit on a VM and compiled it. I guess this
> will have to work for now.
>
>
>
> On Mon, Dec 27, 2021 at 9:27 PM Stuart McLachlan <stuart at lexacorp.com.pg>
> wrote:
>
> > It's ever been thus.
> >
> > Opening an accee with  that's been compiled with a more recent version
> > than you are
> > using.opening it with is frequently problematic.
> >
> > You need to compile on the lowest version that will be using it.
> >
> >
> >
> https://support.microsoft.com/en-us/office/deploy-an-access-application-7bb4f2ba-30ee-458
> >
> > c-a673-102dc34bf14fhttps://
> support.microsoft.com/en-us/office/deploy-an-access-applicatio
> > n-7bb4f2ba-30ee-458c-a673-102dc34bf14f
> > <
> https://support.microsoft.com/en-us/office/deploy-an-access-application-7bb4f2ba-30ee-458c-a673-102dc34bf14fhttps://support.microsoft.com/en-us/office/deploy-an-access-application-7bb4f2ba-30ee-458c-a673-102dc34bf14f
> >
> >
> > Important   Users can't open a compiled binary file by using an earlier
> > version of
> > Access than the version in which it was compiled if the earlier version
> > doesn?t
> > support a feature added in the later version. To resolve this issue,
> > compile the
> > binary file in the Access version your users have installed.
> >
> >
> >
> > On 27 Dec 2021 at 20:15, Ryan W wrote:
> >
> > > I?m not changing bitness. Last week I was using 2013 64. This week
> > > 2021 64.
> > >
> > > None of my desktop clients use 32 bit access anymore.
> > >
> > > Unfortunately the accde file saved under 2021 doesn?t work on 2013
> > > with the same bitness. It throws some errors on startup they weren?t
> > > there with the 2013 saved accde from last week before I upgraded.
> > >
> > > Sent from my iPhone
> > >
> > > > On Dec 27, 2021, at 8:02 PM, John Colby <jwcolby at gmail.com> wrote:
> > > >
> > > > can you do a decompile / compile under the Office 2021 32 bit
> > > > compiler? Send the resulting file to those clients still on 2013.  I
> > > > think the "Bitness" of the compiler is exactly the problem.  A 64
> > > > bit compiler is going to make fundamental changes to pointer lengths
> > > > etc. You might have to run a virtual machine where you install a 32
> > > > bit version of Office 2021 so you can do the compile under the 32
> > > > bit compiler.
> > > >
> > > >
> > > >
> > > >> On Mon, Dec 27, 2021 at 6:35 PM Ryan W <wrwehler at gmail.com> wrote:
> > > >>
> > > >> We're upgrading to Office 2021, I made a small change to a form to
> > > >> fit better with the new UI (the runtime ribbon is a bit taller for
> > > >> some reason) in one of my forms which fixed the form issue for a
> > > >> user currently running Access 2021.
> > > >>
> > > >> However, users who are still on 2013 during this rollout are now
> > > >> getting 2467 coming out of a JIT class John Colby assisted with,
> > > >> and a ribbon button that simply calls DoCmd.OpenForm "MyFormName"
> > > >> now errors out with a vague message.
> > > >>
> > > >> Literally nothing in the DB changed aside from the one form, a
> > > >> decompile, compile then compact&repair and a recompile into an
> > > >> accde and distributed.
> > > >>
> > > >> I've since remedied the update mechanism I use to split 2013 and
> > > >> 2021 accde's into different directories on the server for them to
> > > >> pull down and use... but was curious if anyone had any clues?  I'm
> > > >> not moving across bit-ness or any major changes, no function calls
> > > >> that are erroring out rely on conversion to 64 bit (PtrSafe etc).
> > > >>
> > > >> Shouldn't this front end still function under an older version
> > > >> granted I haven't changed anything that should be a show stopper?
> > > >>
> > > >> The form I changed isn't even the form that the errors on open
> > > >> reference either....
> > > >>
> > > >> The challenge in debugging now is that I do not have an active copy
> > > >> of Access 2013 64 bit that allows for development. Only runtime
> > > >> environments for 2013. -- AccessD mailing list
> > > >> AccessD at databaseadvisors.com
> > > >> https://databaseadvisors.com/mailman/listinfo/accessd Website:
> > > >> http://www.databaseadvisors.com
> > > >>
> > > >
> > > >
> > > > --
> > > > John W. Colby
> > > > Colby Consulting
> > > > --
> > > > 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
> >
> >
> > --
> > 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
>


-- 
John W. Colby
Colby Consulting

From wrwehler at gmail.com  Tue Dec 28 18:46:29 2021
From: wrwehler at gmail.com (Ryan W)
Date: Tue, 28 Dec 2021 18:46:29 -0600
Subject: [AccessD] Access 2021 accde (64 bit) incompatible with Access
 2013 64 bit
In-Reply-To: <CAA_iUE9MC_vknpGLicjnw==FHZvZqafQjLg=9FXY4wqC9qC3Rw@mail.gmail.com>
References: <CAA_iUE9MC_vknpGLicjnw==FHZvZqafQjLg=9FXY4wqC9qC3Rw@mail.gmail.com>
Message-ID: <15694FE2-3FD7-4C8D-8624-F4A30BF466CA@gmail.com>

So far yes the 2013 compiled 64 bit version runs fine on both the 2013 workstations and 2021 workstations. It?s just a PITA to have to send the accdb to a VM just to compile it and send it back up to the file share to distribute. 

Sent from my iPhone

> On Dec 28, 2021, at 6:27 PM, John Colby <jwcolby at gmail.com> wrote:
> 
> ?Did that fix the problem?
> 
>> On Tue, Dec 28, 2021 at 9:15 AM Ryan W <wrwehler at gmail.com> wrote:
>> 
>> Okay fair enough. Your link does say that but Access has been so stale on
>> the development front for some time that the differences between 2013 and
>> 2021 are minimal AT BEST.
>> 
>> I've installed Access 2013 64-bit on a VM and compiled it. I guess this
>> will have to work for now.
>> 
>> 
>> 
>> On Mon, Dec 27, 2021 at 9:27 PM Stuart McLachlan <stuart at lexacorp.com.pg>
>> wrote:
>> 
>>> It's ever been thus.
>>> 
>>> Opening an accee with  that's been compiled with a more recent version
>>> than you are
>>> using.opening it with is frequently problematic.
>>> 
>>> You need to compile on the lowest version that will be using it.
>>> 
>>> 
>>> 
>> https://support.microsoft.com/en-us/office/deploy-an-access-application-7bb4f2ba-30ee-458
>>> 
>>> c-a673-102dc34bf14fhttps://
>> support.microsoft.com/en-us/office/deploy-an-access-applicatio
>>> n-7bb4f2ba-30ee-458c-a673-102dc34bf14f
>>> <
>> https://support.microsoft.com/en-us/office/deploy-an-access-application-7bb4f2ba-30ee-458c-a673-102dc34bf14fhttps://support.microsoft.com/en-us/office/deploy-an-access-application-7bb4f2ba-30ee-458c-a673-102dc34bf14f
>>> 
>>> 
>>> Important   Users can't open a compiled binary file by using an earlier
>>> version of
>>> Access than the version in which it was compiled if the earlier version
>>> doesn?t
>>> support a feature added in the later version. To resolve this issue,
>>> compile the
>>> binary file in the Access version your users have installed.
>>> 
>>> 
>>> 
>>>> On 27 Dec 2021 at 20:15, Ryan W wrote:
>>> 
>>>> I?m not changing bitness. Last week I was using 2013 64. This week
>>>> 2021 64.
>>>> 
>>>> None of my desktop clients use 32 bit access anymore.
>>>> 
>>>> Unfortunately the accde file saved under 2021 doesn?t work on 2013
>>>> with the same bitness. It throws some errors on startup they weren?t
>>>> there with the 2013 saved accde from last week before I upgraded.
>>>> 
>>>> Sent from my iPhone
>>>> 
>>>>> On Dec 27, 2021, at 8:02 PM, John Colby <jwcolby at gmail.com> wrote:
>>>>> 
>>>>> can you do a decompile / compile under the Office 2021 32 bit
>>>>> compiler? Send the resulting file to those clients still on 2013.  I
>>>>> think the "Bitness" of the compiler is exactly the problem.  A 64
>>>>> bit compiler is going to make fundamental changes to pointer lengths
>>>>> etc. You might have to run a virtual machine where you install a 32
>>>>> bit version of Office 2021 so you can do the compile under the 32
>>>>> bit compiler.
>>>>> 
>>>>> 
>>>>> 
>>>>>> On Mon, Dec 27, 2021 at 6:35 PM Ryan W <wrwehler at gmail.com> wrote:
>>>>>> 
>>>>>> We're upgrading to Office 2021, I made a small change to a form to
>>>>>> fit better with the new UI (the runtime ribbon is a bit taller for
>>>>>> some reason) in one of my forms which fixed the form issue for a
>>>>>> user currently running Access 2021.
>>>>>> 
>>>>>> However, users who are still on 2013 during this rollout are now
>>>>>> getting 2467 coming out of a JIT class John Colby assisted with,
>>>>>> and a ribbon button that simply calls DoCmd.OpenForm "MyFormName"
>>>>>> now errors out with a vague message.
>>>>>> 
>>>>>> Literally nothing in the DB changed aside from the one form, a
>>>>>> decompile, compile then compact&repair and a recompile into an
>>>>>> accde and distributed.
>>>>>> 
>>>>>> I've since remedied the update mechanism I use to split 2013 and
>>>>>> 2021 accde's into different directories on the server for them to
>>>>>> pull down and use... but was curious if anyone had any clues?  I'm
>>>>>> not moving across bit-ness or any major changes, no function calls
>>>>>> that are erroring out rely on conversion to 64 bit (PtrSafe etc).
>>>>>> 
>>>>>> Shouldn't this front end still function under an older version
>>>>>> granted I haven't changed anything that should be a show stopper?
>>>>>> 
>>>>>> The form I changed isn't even the form that the errors on open
>>>>>> reference either....
>>>>>> 
>>>>>> The challenge in debugging now is that I do not have an active copy
>>>>>> of Access 2013 64 bit that allows for development. Only runtime
>>>>>> environments for 2013. -- AccessD mailing list
>>>>>> AccessD at databaseadvisors.com
>>>>>> https://databaseadvisors.com/mailman/listinfo/accessd Website:
>>>>>> http://www.databaseadvisors.com
>>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> John W. Colby
>>>>> Colby Consulting
>>>>> --
>>>>> 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
>>> 
>>> 
>>> --
>>> 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
>> 
> 
> 
> -- 
> John W. Colby
> Colby Consulting
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> https://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com

From jwcolby at gmail.com  Tue Dec 28 18:54:36 2021
From: jwcolby at gmail.com (John Colby)
Date: Tue, 28 Dec 2021 19:54:36 -0500
Subject: [AccessD] Access 2021 accde (64 bit) incompatible with Access
 2013 64 bit
In-Reply-To: <15694FE2-3FD7-4C8D-8624-F4A30BF466CA@gmail.com>
References: <CAA_iUE9MC_vknpGLicjnw==FHZvZqafQjLg=9FXY4wqC9qC3Rw@mail.gmail.com>
 <15694FE2-3FD7-4C8D-8624-F4A30BF466CA@gmail.com>
Message-ID: <CAA_iUE-kLDGffLyQcrxyMHDEb7ejg6xzKZGf=E3S4-rFwjPsXA@mail.gmail.com>

I understand.  A VM to handle old versions is a messy but useful trick.

On Tue, Dec 28, 2021 at 7:46 PM Ryan W <wrwehler at gmail.com> wrote:

> So far yes the 2013 compiled 64 bit version runs fine on both the 2013
> workstations and 2021 workstations. It?s just a PITA to have to send the
> accdb to a VM just to compile it and send it back up to the file share to
> distribute.
>
> Sent from my iPhone
>
> > On Dec 28, 2021, at 6:27 PM, John Colby <jwcolby at gmail.com> wrote:
> >
> > ?Did that fix the problem?
> >
> >> On Tue, Dec 28, 2021 at 9:15 AM Ryan W <wrwehler at gmail.com> wrote:
> >>
> >> Okay fair enough. Your link does say that but Access has been so stale
> on
> >> the development front for some time that the differences between 2013
> and
> >> 2021 are minimal AT BEST.
> >>
> >> I've installed Access 2013 64-bit on a VM and compiled it. I guess this
> >> will have to work for now.
> >>
> >>
> >>
> >> On Mon, Dec 27, 2021 at 9:27 PM Stuart McLachlan <
> stuart at lexacorp.com.pg>
> >> wrote:
> >>
> >>> It's ever been thus.
> >>>
> >>> Opening an accee with  that's been compiled with a more recent version
> >>> than you are
> >>> using.opening it with is frequently problematic.
> >>>
> >>> You need to compile on the lowest version that will be using it.
> >>>
> >>>
> >>>
> >>
> https://support.microsoft.com/en-us/office/deploy-an-access-application-7bb4f2ba-30ee-458
> >>>
> >>> c-a673-102dc34bf14fhttps://
> >> support.microsoft.com/en-us/office/deploy-an-access-applicatio
> >>> n-7bb4f2ba-30ee-458c-a673-102dc34bf14f
> >>> <
> >>
> https://support.microsoft.com/en-us/office/deploy-an-access-application-7bb4f2ba-30ee-458c-a673-102dc34bf14fhttps://support.microsoft.com/en-us/office/deploy-an-access-application-7bb4f2ba-30ee-458c-a673-102dc34bf14f
> >>>
> >>>
> >>> Important   Users can't open a compiled binary file by using an earlier
> >>> version of
> >>> Access than the version in which it was compiled if the earlier version
> >>> doesn?t
> >>> support a feature added in the later version. To resolve this issue,
> >>> compile the
> >>> binary file in the Access version your users have installed.
> >>>
> >>>
> >>>
> >>>> On 27 Dec 2021 at 20:15, Ryan W wrote:
> >>>
> >>>> I?m not changing bitness. Last week I was using 2013 64. This week
> >>>> 2021 64.
> >>>>
> >>>> None of my desktop clients use 32 bit access anymore.
> >>>>
> >>>> Unfortunately the accde file saved under 2021 doesn?t work on 2013
> >>>> with the same bitness. It throws some errors on startup they weren?t
> >>>> there with the 2013 saved accde from last week before I upgraded.
> >>>>
> >>>> Sent from my iPhone
> >>>>
> >>>>> On Dec 27, 2021, at 8:02 PM, John Colby <jwcolby at gmail.com> wrote:
> >>>>>
> >>>>> can you do a decompile / compile under the Office 2021 32 bit
> >>>>> compiler? Send the resulting file to those clients still on 2013.  I
> >>>>> think the "Bitness" of the compiler is exactly the problem.  A 64
> >>>>> bit compiler is going to make fundamental changes to pointer lengths
> >>>>> etc. You might have to run a virtual machine where you install a 32
> >>>>> bit version of Office 2021 so you can do the compile under the 32
> >>>>> bit compiler.
> >>>>>
> >>>>>
> >>>>>
> >>>>>> On Mon, Dec 27, 2021 at 6:35 PM Ryan W <wrwehler at gmail.com> wrote:
> >>>>>>
> >>>>>> We're upgrading to Office 2021, I made a small change to a form to
> >>>>>> fit better with the new UI (the runtime ribbon is a bit taller for
> >>>>>> some reason) in one of my forms which fixed the form issue for a
> >>>>>> user currently running Access 2021.
> >>>>>>
> >>>>>> However, users who are still on 2013 during this rollout are now
> >>>>>> getting 2467 coming out of a JIT class John Colby assisted with,
> >>>>>> and a ribbon button that simply calls DoCmd.OpenForm "MyFormName"
> >>>>>> now errors out with a vague message.
> >>>>>>
> >>>>>> Literally nothing in the DB changed aside from the one form, a
> >>>>>> decompile, compile then compact&repair and a recompile into an
> >>>>>> accde and distributed.
> >>>>>>
> >>>>>> I've since remedied the update mechanism I use to split 2013 and
> >>>>>> 2021 accde's into different directories on the server for them to
> >>>>>> pull down and use... but was curious if anyone had any clues?  I'm
> >>>>>> not moving across bit-ness or any major changes, no function calls
> >>>>>> that are erroring out rely on conversion to 64 bit (PtrSafe etc).
> >>>>>>
> >>>>>> Shouldn't this front end still function under an older version
> >>>>>> granted I haven't changed anything that should be a show stopper?
> >>>>>>
> >>>>>> The form I changed isn't even the form that the errors on open
> >>>>>> reference either....
> >>>>>>
> >>>>>> The challenge in debugging now is that I do not have an active copy
> >>>>>> of Access 2013 64 bit that allows for development. Only runtime
> >>>>>> environments for 2013. -- AccessD mailing list
> >>>>>> AccessD at databaseadvisors.com
> >>>>>> https://databaseadvisors.com/mailman/listinfo/accessd Website:
> >>>>>> http://www.databaseadvisors.com
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> John W. Colby
> >>>>> Colby Consulting
> >>>>> --
> >>>>> 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
> >>>
> >>>
> >>> --
> >>> 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
> >>
> >
> >
> > --
> > John W. Colby
> > Colby Consulting
> > --
> > 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
>


-- 
John W. Colby
Colby Consulting

From jimdettman at verizon.net  Wed Dec 29 06:18:05 2021
From: jimdettman at verizon.net (Jim Dettman)
Date: Wed, 29 Dec 2021 07:18:05 -0500
Subject: [AccessD] Access 2021 accde (64 bit) incompatible with Access
 2013 64 bit
In-Reply-To: <61CBA801.12497.21DC1098@stuart.lexacorp.com.pg>
References: <CAA_iUE8_pjWi_74tOQPptE_BOFMgp1uDnj0N7Kw=aDyMO91B3g@mail.gmail.com>,
 <61CA841B.12303.1D67D55D@stuart.lexacorp.com.pg>,
 <CAFXiSd8eic=V6jsS+gQ5fG8zd4wWZh0bnxQrVz4_qO0tQBM5Fg@mail.gmail.com>
 <61CBA801.12497.21DC1098@stuart.lexacorp.com.pg>
Message-ID: <03bb01d7fcae$225df150$6719d3f0$@verizon.net>


 Yes, along with support for DateTime2 in SQL, more robust ODBC connection
handling, a new Linked Table Manager, UI refinements, numerous improvements
in the SQL Editor, and quite a number of other things.

 Access has not been standing still by any means.

Jim.

-----Original Message-----
From: AccessD On Behalf Of Stuart McLachlan
Sent: Tuesday, December 28, 2021 7:13 PM
To: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] Access 2021 accde (64 bit) incompatible with Access
2013 64 bit

One major difference between 2013 and 2021 is the LargeNumber/BigInt data
type 
introduced in 2016.


On 28 Dec 2021 at 8:15, Ryan W wrote:

> Okay fair enough. Your link does say that but Access has been so stale
> on the development front for some time that the differences between
> 2013 and 2021 are minimal AT BEST.
> 
> I've installed Access 2013 64-bit on a VM and compiled it. I guess
> this will have to work for now.
> 
> 
> 

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


From wrwehler at gmail.com  Wed Dec 29 06:53:06 2021
From: wrwehler at gmail.com (Ryan Wehler)
Date: Wed, 29 Dec 2021 06:53:06 -0600
Subject: [AccessD] Access 2021 accde (64 bit) incompatible with Access
 2013 64 bit
In-Reply-To: <03bb01d7fcae$225df150$6719d3f0$@verizon.net>
References: <03bb01d7fcae$225df150$6719d3f0$@verizon.net>
Message-ID: <B3DBEB68-1380-4DEB-8E12-34B342D61537@gmail.com>

What?s the skinny on the ODB handling? The rest I knew about but still find that minimal for 8 years of development time between 2013 and 2021. We?ve yet to see the Monaco editor that was promised this year, too. 

Not sure I call the giant red streak along the top (since 2016?) much of a UI refinement. In fact I had users come ask me how to get rid of it already. 

> On Dec 29, 2021, at 6:18 AM, Jim Dettman via AccessD <accessd at databaseadvisors.com> wrote:
> 
> ?
> Yes, along with support for DateTime2 in SQL, more robust ODBC connection
> handling, a new Linked Table Manager, UI refinements, numerous improvements
> in the SQL Editor, and quite a number of other things.
> 
> Access has not been standing still by any means.
> 
> Jim.
> 
> -----Original Message-----
> From: AccessD On Behalf Of Stuart McLachlan
> Sent: Tuesday, December 28, 2021 7:13 PM
> To: Access Developers discussion and problem solving
> <accessd at databaseadvisors.com>
> Subject: Re: [AccessD] Access 2021 accde (64 bit) incompatible with Access
> 2013 64 bit
> 
> One major difference between 2013 and 2021 is the LargeNumber/BigInt data
> type 
> introduced in 2016.
> 
> 
>> On 28 Dec 2021 at 8:15, Ryan W wrote:
>> 
>> Okay fair enough. Your link does say that but Access has been so stale
>> on the development front for some time that the differences between
>> 2013 and 2021 are minimal AT BEST.
>> 
>> I've installed Access 2013 64-bit on a VM and compiled it. I guess
>> this will have to work for now.
>> 
>> 
>> 
> 
> -- 
> 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

From jimdettman at verizon.net  Wed Dec 29 07:18:56 2021
From: jimdettman at verizon.net (Jim Dettman)
Date: Wed, 29 Dec 2021 08:18:56 -0500
Subject: [AccessD] Access 2021 accde (64 bit) incompatible with Access
 2013 64 bit
In-Reply-To: <B3DBEB68-1380-4DEB-8E12-34B342D61537@gmail.com>
References: <03bb01d7fcae$225df150$6719d3f0$@verizon.net>
 <B3DBEB68-1380-4DEB-8E12-34B342D61537@gmail.com>
Message-ID: <03c801d7fcb6$a27d0a30$e7771e90$@verizon.net>

<< What?s the skinny on the ODB handling? >>

It's in here:

https://support.microsoft.com/en-us/office/what-s-new-in-access-2019-f52c5317-3494-4105-9c56-5a2abb8e0f87

about halfway down.

 Monaco was delayed, but there still have been improvements made to the query editor.  There is now a find and replace feature, and you can directly open a table in either view (data or design), or choose "Size to Fit" in the shortcut menu so you can see the full table name and fields.  That?s covered here:

https://support.microsoft.com/en-us/office/what-s-new-in-access-2021-2c5c0766-b22b-4b81-a222-a791a8b5b54b

 and you can view a demo of those new features here:

https://www.youtube.com/watch?v=m4xTwmflTcI

<< The rest I knew about but still find that minimal for 8 years of development time between 2013 and 2021>>

  There are other things as well, like the graphs and  a lot of minor things you might not notice, like wider clickable areas in some of the UI elements.

  Access 2016 didn't have much (most of the changes there were not visible), but everything since that has added significant features that you do and I would not say they are minimal.   

Jim.

-----Original Message-----
From: Ryan Wehler 
Sent: Wednesday, December 29, 2021 7:53 AM
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Cc: Jim Dettman <jimdettman at verizon.net>
Subject: Re: [AccessD] Access 2021 accde (64 bit) incompatible with Access 2013 64 bit

What?s the skinny on the ODB handling? The rest I knew about but still find that minimal for 8 years of development time between 2013 and 2021. We?ve yet to see the Monaco editor that was promised this year, too. 

Not sure I call the giant red streak along the top (since 2016?) much of a UI refinement. In fact I had users come ask me how to get rid of it already. 

> On Dec 29, 2021, at 6:18 AM, Jim Dettman via AccessD <accessd at databaseadvisors.com> wrote:
> 
> ?
> Yes, along with support for DateTime2 in SQL, more robust ODBC connection
> handling, a new Linked Table Manager, UI refinements, numerous improvements
> in the SQL Editor, and quite a number of other things.
> 
> Access has not been standing still by any means.
> 
> Jim.
> 
> -----Original Message-----
> From: AccessD On Behalf Of Stuart McLachlan
> Sent: Tuesday, December 28, 2021 7:13 PM
> To: Access Developers discussion and problem solving
> <accessd at databaseadvisors.com>
> Subject: Re: [AccessD] Access 2021 accde (64 bit) incompatible with Access
> 2013 64 bit
> 
> One major difference between 2013 and 2021 is the LargeNumber/BigInt data
> type 
> introduced in 2016.
> 
> 
>> On 28 Dec 2021 at 8:15, Ryan W wrote:
>> 
>> Okay fair enough. Your link does say that but Access has been so stale
>> on the development front for some time that the differences between
>> 2013 and 2021 are minimal AT BEST.
>> 
>> I've installed Access 2013 64-bit on a VM and compiled it. I guess
>> this will have to work for now.
>> 
>> 
>> 
> 
> -- 
> 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