Easily recover lost and permanently deleted data with the help of EDB to PST Converter application that is designed by using the rich algorithm and the best technology. It helps the user to convert the required folders from priv 1.edb file and pub 1.edb file included with the email, notes, tasks, attachments, contact, draft, inbox and calendar (For, CC, From, Date, Time, Subject, Object, and Cc). It not only recovers data but also converts into new PST file format included with all properties of email like To, Cc, From, Date, Time, Subject, Object, and Bcc. Using it the user can easily export those file which they want to convert from EDB data file to PST file format without any hassle. It is compatible to export one as well as more than one file into PST, EML, EMLX, MSG, vCal, vCard, and MBOX file format with 100% accurate result. With the assistance of this application you can migrate the data of EDB file into Office365 & Live Exchange Server. It provide an accurate result that is better than your expectations. It provide free demo version that allows to migrate 30 emails per folder without any hassle. You can also return it under 30 emails if you have any issue with this application. This is the number one tool for the conversion work.

Read More: https://www.inquitsoftware.com/en/pages/edb-to-pst-converter.html

Access returns an incorrect record ID when a form is bound to an SQL Server table that has an 'insert trigger' that inserts a record into 'another' table. The record ID returned is actually the record ID of the trigger inserted record into the 'other' table. This is because Access calls SQL Server for @@IDENTITY rather than SCOPE_IDENTITY() when inserting a new record. This particularly affects SQL Server tables that are 'replicated' as these tables have an MS shipped 'insert trigger' on the table for use in replication. We have an MS Support Case # 23043471 where we have had no resolution ...

Seems to be a Bug!
Filtering on a filed containing ی (persian ye = unicode 1740) finds ي (arabic ye =1610) on linked tables; while searching and sorting are correct. this bug does not appear on local tables, just on linked tables.

Test environment:
- data table reside on MS SQL Server 2017
- Data fields are NVARCHAR
- MS ACCESS 2016 linked table over ODBC 11

Please type with Persian keyboard layout

this bug existed from previous versions and is know to Persian language users and I don't know if someone has reported or not before.

I can provide more information in case of need
Thanks

I've been looking more into Power Apps, and I think it would be great for you to work with the Power Apps team to provide a web and mobile solution to what Access can do today on the premises of a server. Because there is unfortunately no web version of Access, maybe Power Apps can help solve this problem? Ideally, we should be able to continue moving (and linking) Access data into SQL and then create a Power App on top of the "Access-created" data from SQL; essentially viewing a Power Application that looks exactly like access but online and on the phone.

• make it possible to select a subset of fields from a Salesforce object

Primarily, this would make it possible to work with SF objects that have exceeded the limit of 256 or whatever it is for Access. There would be other benefits too. But this alone would make the Salesforce/Access integration much more doable (right now I have to use an intermediary such as power query or sql server for these larger objects)

• make it possible to link to Salesforce reports. (less important but very helpful)

1 is really very necessary. I'd go so far as to say that without that the feature is only half baked, and not particularly useful.