Geek Answers Handbook

Adding a new column to SQL SERVER, but it does not appear in access

access is the interface, and SQL Server is the backend

I open a specific table in access. I have no problem editing the data in this table using the SQL server and then displaying the changes in access; however, when I add a new field in the sql server, the changes are not reflected in access.

I open the table as a data table and does not show the new field that I added in access. ive opened and closed the file and still does not work.

Does anyone know what is going on here?

+6
sql-server ms-access
source share
3 answers

You may need to update the SQL Server table in Access using the Linked Table Manager.

+9
source share

This SO Q & A seems to cover similar territory.

+2
source share

I cannot add a comment, but I would like to add ... because it annoys me.

This is the same story not only in MS Access, in SSMS (MS SQL Server Management Studio, even with the latest version of MS SQL Server 2008 R2) with its own "native" mdf database and tables from it.

If you change the contents of the table through another window / tab or instance of SSMS (via TSQL or through interactive editing), then the contents shown in the editing table that has already opened for the interactive table are not updated, although it is updated by the non-documented Ctrl + R.
And it is not available in SSMS GUI (without entering a menu, without a button, etc.) !!!
Any browser / webapp can be easily configured to update content, but not for the MS desktop GUI.

But if for ALTER TABLE, for example, to add a column, then an already opened tab with a table (SSMS) cannot reflect changes (cannot display a changed table , for example, with adding a column), even by pressing Ctrl + R.
It is necessary to close the tab (window) with the table and open it again
(right-click on the table in SSMS ObjectExplorer → Change tio 200 rows) !!!

I remember I discovered a bug in Microsoft Connect reviews, and it was closed because it was a "design" feature!

Still IMHO this is a mistake and requires brute force (/ ugly GUI actions) to get around it

+1
source share

More articles:


All Articles