in office access 2007 we used to be able to import text files that have an extension other than .txt, many businesses have files that are text files that do not have .txt extension and although I can change the extension to .txt, it is very time consuming when I have thousands of these files

People asked for exporting and importing json data but what about linking to json data?

Fix Access so using an ADODB recordset works the same as a linked backend table

When I set the form recordset to an ADODB recordset, things no longer work the same as when I just use a linked table.

For example, a Subdatasheet no longer uses the "Link Master Fields" and "Link Child Fields" form properties.

When the end user tries to use the autofilters, they just get an error message.

Currently, the developer needs to go through the process of importing a file into a database in order to create or edit an import/export spec in the MSysIMEXSpecs table. True, the MSysIMEXColumns can be edited directly in the table, but overall, the process is not very user friendly. There needs to be functionality to create/edit import/export specs without have to pretend that one is importing an external file.

Since Office Click-to-Run Installs can result in the ODBC / OLE-DB Drivers for ACE NOT being visible to the system outside of the VDI install environment, we need a CURRENT version of the ACE engine redistributable package (the last one being from Access 2010 - 6 YEARS AGO!)

For more info see: https://support.microsoft.com/en-us/kb/2874601

Perhaps an error.description2 property which we can reference which stores the error returned from SQL about the true problem. Right now it is very difficult to trouble shoot.

Thanks.

It would be more intuitive to link sql tables WITHOUT the owner prefix.

You can no longer link to an ACCDE back end. This needs to be fixed!

I have some saved imports that pull in multiple tables from our ERP system. I believe it would be informative to know which "step" in the import is active by showing the table name on the status bar. Right now it shows "Importing. Press and hold ESC to stop." Expanding that to "Importing table xxxxxxxx - Press and hold ESC to stop."

Improve the interactive data-exchange between ACCESS and VISIO.

A visio worksheet should be integrable into a form like a chart, and the data of selected shapes could be made available as a single record.

when importing data from a text file allow a field to be defined by a regular expression.

Create a link to Outlook WebApp contacts folder.
The connector already existing depends on an Outlook PC/MAC version to get the data from. I suggest creating a connector directly to the contact's server folder.
That way it would be possible to edit easily a list of Outlook WebApp contacts in Access.

How Can I Convert MDE To MDB Wth VBA , If Unlock Possible?!!! Or Export Forms Or Reports To New Application

A frequent task in Access is to import some or all database objects from an existing database into a blank new database. After that, we must painstakingly set all non-standard VBA references in the new database the same way as in the old one.
It would be nice if we could specify in the Import Objects dialog which references should be copied from the existing database into the new one.

When I try to export an Access table into an Oracle database it doesn't retain the input field formats. Everything is converted into a string and the indices are lost. I've contacted Microsoft about this before but got no meaningful response, presumably for petty proprietary reasons.

In MS Access its easy to add descriptions to fields in table editor. These descriptions are neither taken over when using ssma nor are they brought back to Access when already existing in sql server.

I've written a vba-script that creates an T_SQL script to create all field descriptions of a table. But even if descriptions exists they are not reshown in the linked table.