Dataverse

12 Topics

Access Releases 7 Issue Fixes in Version 2311 (Released November 25th, 2023)
Our newest round of Access bug fixes was released on November 25th, 2023. In this blog post, we highlight some of the fixed issues that our Access engineers released in the current monthly channel.
lindalu-MSFT
Aug 13, 2025 Place Access Blog
9.4KViews
3likes
29Comments
Access Releases 7 Issue Fixes in Version 2310 (Released October 25th, 2023)
Our newest round of Access bug fixes was released on October 25th, 2023. In this blog post, we highlight some of the fixed issues that our Access engineers released in the current monthly channel. If you see a bug that impacts you, and if you are on the current monthly channel Version 2310, you should have these fixes. Make sure you are on Access Build # 16.0.16924.20106 or greater.
lindalu-MSFT
Aug 13, 2025 Place Access Blog
4.6KViews
2likes
4Comments
Access Releases 6 Issue Fixes in Version 2306 (Released June 26th, 2023)
Our newest round of Access bug fixes was released on June 26th, 2023. In this blog post, we highlight some of the fixed issues that our Access engineers released in the current monthly channel.
lindalu-MSFT
Aug 13, 2025 Place Access Blog
6KViews
4likes
2Comments
Access Releases 6 Issue Fixes in Version 2303 (Released March 28, 2023)
Our newest round of Access bug fixes was released on March 28, 2023. In this blog post, we are highlighting some of the fixed issues that our Access engineers released in the current monthly channel.
lindalu-MSFT
Aug 13, 2025 Place Access Blog
6KViews
4likes
0Comments
Access Releases 4 Issue Fixes in Version 2212 (Released January 4, 2023)
Our newest round of Access bug fixes was released on January 4th. In this blog post, we highlight some of the fixed issues that our Access engineers released in the current monthly channel.
lindalu-MSFT
Aug 13, 2025 Place Access Blog
11KViews
6likes
1Comment
Access Releases 8 Issue Fixes in Version 2211 (Released December 6, 2022)
Our newest round of Access bug fixes was released on December 6th. In this blog post, we highlight some of the fixed issues that our Access engineers released in the current monthly channel.
lindalu-MSFT
Aug 13, 2025 Place Access Blog
7.2KViews
9likes
0Comments
Access Releases 5 Issue Fixes in Version 2208 (Released Aug 31)
We have several issues fixed related to Dataverse, including a proxy issue several customers reported in our blogs last month
Michael_Aldridge
Aug 13, 2025 Place Access Blog
7.1KViews
2likes
0Comments
New Access Fixes in Version 2206 (Released June 29)
17 New Fixes, Make sure you are on Access Build # 16.0.15330.20196 or greater to get these
Michael_Aldridge
Aug 13, 2025 Place Access Blog
9.3KViews
8likes
0Comments
Access Issues Fixed in the May 2022 Monthly Release
A new tradition! Check out the issues fixed in May's current channel release. Make sure you have version 2205 (build 16.0.15225.20000 or greater) to get these fixes
Michael_Aldridge
Aug 13, 2025 Place Access Blog
152KViews
6likes
16Comments
update dataverse table with dataverse primary key results in datatype error
Hi all. I have an annoying issue. I use MS access front end, dataverse backend, I'm using a simple bit of VBA code, to add a new record in a table. This is triggered by clicking a button on a form. Once the new record is created, I then want to add the dataverse primary key of the form to that new record. This all works fine when using numeric access primary keys, but I am trying to start using the dataverse primary keys which I think are string and this is throwing up datamismatch errors. Code: Private Sub AddEndorsement() Dim rs As DAO.Recordset On Error GoTo Errorhandle Set rs = CurrentDb.OpenRecordset("Endorsements") With rs .AddNew !Policies = Me.Policies .Update .MoveLast .Bookmark = .LastModified End With rs.Close Set rs = Nothing Exit Sub Errorhandler: MsgBox "Error #: " & Err.Number & vbCrLf & vbCrLf & Err.Description End Sub the error it throws up when trying to add the record is 3421, data type conversion error so clearly a data mismatch on !policies and me.policies. However from all I can see they are the same data type. I have a text box on the form that shows me.policies (the primary key ) correctly as {343very long code}. When I check the datatype it is 8. However, in VBA debug window the same value is shown as "?????" which is odd. Endorsement.policies stores the foreign key successfully for other records . The data type in dataverse is "Lookup" but I assume underlying it still means string. Any ideas?
Solved
TheJaks
Jun 12, 2024 Place Access
1.6KViews
0likes
7Comments