What is your question?

Well, do you want a bound or unbound form? Do you want data sheet view or controls? What process are you implementing? How does your data model look like (cardinalities?)?

Is there a 64bit version of the msFlexgrid available?

Even the newest commercial siblings of Grid-alike controls are not usable under 64bit Access as for the time being is a very small market... since there isn't a clear advantage of using 64bit Access.
EDIT1 : Here you can find all the "benefits" of Using 64-bit Access...too bad there aren't any real user case except for Large Number datatype.

I realize that there are no real benefits of running 64bit access, but alas Access is just one cog in the office suite, and people might install office 64bit to get support for larger datasheets in excel.

Add to that, from Office 2019 and on, the default installation is 64bit. I would therefore strongly recommend against a solution that will only work on 32 bit.

the default installation is 64bit

Sometimes you need to take a look behind the curtain...For years Ms has being recommending 32bit Office against 64 bit but it seems that conflicts with their marketing agenda so i guess the time has come to force 64bit to avoid the fuss....of course they don't care about the true user needs ...i have being reading about people complaining for the lack of extra controls ...the answer was : "Just gather more votes to consider it"....controls that have being widely used in the past (like Treeview)
IMHO if you are developing for an in house solution that would never take off besides the company premises then 32bit/64bit makes no difference ...and to be honest Access targets "local" development...
On the other hand i don't see any real advantage so its up to developer to pick...but personally i would like to have code pieces working right away without wasting work hours ...
Back when AMD released the 1st 64bit processor there were huge talks and promises about the wonderful 64bit applications...the years have passed and besides a handful of applications that really take advantage of 64bit (like 3D) the revolution hasn't came...
To me its just a natural confusion...you get a 64 OS why not to use a 64bit Office....too bad there are cons/pros to consider before installing.

@John,

  On this:

EDIT1 : Here you

 You are not pointing to the current content as you are pointing to the Office 2016 tab; a lot has changed in the past three years.  This is the current link:

https://support.office.com/en-ie/article/choose-between-the-64-bit-or-32-bit-version-of-office-2dee7807-8f95-4d0c-b5fe-6c6f49b8d261#32or64Bit=Newer_Versions

 for Office 2019 and forward (hard to say there is a "version" anymore) and at the end, there is one specific reason for using 64 bit Access that is  given:

You’re working with the Large Number data type in Access,

 also as we have discussed in other threads, the other reason is the process address space, which right now, Access is limited to 2GB.   While that's not a major problem at the moment, it is becoming a problem.   More and more posts are showing up where users are getting the "out of system resources" messages with the latest releases.

So while I certainly would agree that we are not yet there with Active-x controls, if you don't use them there is no reason not to switch to 64 bit at this time and there are benefits over 32 bit.    If you do use them, then it's time to start pushing for 64 bit versions of them or find alternatives, which I think is what Ander's was trying to get at.  No sense in building a solution if it's not going to be workable going forward.

I would not be shocked either if in the next five years or six years Microsoft no longer offered 32 bit Office.   With that said, I have no idea if that will be the case or not, but the push is on to move to 64 bit and not just from Microsoft.

At the very least, you should be looking at what it will take you to get there and always give that consideration when your working on solutions.

There will be a day when we leave 32 behind and that day is coming.

Jim.

I reckon this would take roughly a decade so probably it would be wiser to move to another platform than yo argue about 32 vs 64.
One thing i know for sure is that my copy of  Office 2016 is going to accompany me for many years more

I reckon this would take roughly a decade ...

 umm...don't think it will be that long.  Could be, but we've already had 64 bit in Office since 2010.

 Certainly Access 2016 will be workable for many years and there's nothing wrong with using it well into the future.  Even 2019 and Office 365 are still available in 32 bit.   Right now, 64 bit is just the default install.     But once Microsoft moves onto 64 bit only,  you'll be stuck with the feature set that it offers.  If you can live with that, then you will be set for a long time.  I don't see 32 bit support dying out in windows for quite some time.

 But as you pointed out, it depends on the type of development you do to an extent (in-house vs out).   I think though that even in-house will become difficult.

 From Office 2010 and up, any version of Office will need to be the same bitness, and all products within the install need to be the same.  So by saying "I'll stick with 32 bit Access", that means everything else (Excel, Word, Outlook, etc) as well will be 32 bit and that will limit you.  Especially as we move forward over the next few years.

Also one thing with Access is that you can't get around the large number data type limitations using 32 bit.   Yes it's supported in 32 bit, but only to an extent.  The only clean way of handling the large number data type is with the 64 bit edition.   Something like that may be out of your control, i.e. you develop apps that run against databases that are not yours.

There is a very mixed bag of Access apps out there and some may be able to live with 32 bit Office for quite some time.  Heck I still have clients on Access 2000!    But I see that segment narrowing more and more as we move forward over the next five or six years.

Sooner or later everyone will need to get over the 64 bit hump just as we did with 16 bit.

Jim.

All of this went way over my head.  But thanks to those that contributed.  I've decided to go a different route.

Anything we can help you understand about what's been discussed or with your new direction on this?

Jim.

Thanks Jim, but not at this time.  I went off in a different direction which seems to be working out.  I do appreciate the offer however.

OK.

Jim.