SOLVED

Linking a File Table from Microsoft SQL Server to a table within Microsoft Access 2016

Copper Contributor

I've used the standard method of linking tables from a Microsoft SQL 2012 Database into an Access 2016 Database. Every table linked correctly except for a File Table. Within Access, the linked table displays the File Table's fields but not the records. How can I create a linked table within Access that correctly displays all the contents of the File Table that are within the SQL database?

 

I've tried using updated drivers to create the DSN to allow for connection to the SQL server. There is an integrated test within the DSN creation wizard that displays the connection is successful.

 

I expected the linked table within Access to display the contents of the File Table within the SQL database, but it displays the following images and an ODBC--call failed error message:

 

 

2 Replies

@iaskey 

 

I think you can not link a FileTable as usual. FileTables extend the capabilities of the FILESTREAM feature of SQL Server.

 

Maybe you can do "something" with the FileTable with a "passtrough query".  I think the solution would be solving it with VBA. Here is a link to an article about connecting to the FileStream table.

https://docs.microsoft.com/en-us/sql/relational-databases/blob/create-client-applications-for-filest...

best response confirmed by iaskey (Copper Contributor)
Solution

@testmuts Thank you for your response! The issue was a path_locator field in the FileTable. For some reason, there are problems with creating a linked table with the datatype of that field in Access. I was able to avoid creating a linked table with this field by creating a view in SQL Server that did not contain that field. I then did a dsnLess connection using VBA to that view in SQL Server. It worked well after that!

1 best response

Accepted Solutions
best response confirmed by iaskey (Copper Contributor)
Solution

@testmuts Thank you for your response! The issue was a path_locator field in the FileTable. For some reason, there are problems with creating a linked table with the datatype of that field in Access. I was able to avoid creating a linked table with this field by creating a view in SQL Server that did not contain that field. I then did a dsnLess connection using VBA to that view in SQL Server. It worked well after that!

View solution in original post