I do a fair amount of data entry that involves date data into a database table. I can use the Ctrl-' function to add to the field the data in the same field directly above it. This is great. But I have to enter a lot of records with dates, and the new record is for a different date, usually the next date on the calendar. So if there was a function Ctrl-", I would be able to directly add the next day to this record when compared to the record above it. For example if Record 12 has a date of 6/1/2020, I could go to Record 12 and in the same field type Ctrl-", and 6/2/2020 would be entered into that record in Record 13.

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

hi

When I use linked table manager to Reconnect tables VIEW the Key deleted -- in ms access 2019 (365)

VIEW -SQL
for example
dbo_movment (SQL )
The problem is only in VIEW

in Another table (SQL ) has no problem

Previous versions of Access had no problem

The problem is only in the 2019 access

The issue is also in the version 64BIT and also In version 32BIT

How to solve the problem ?

I use SQL2016
With whom I also worked with Access 2016
When I moved to Access 2019
Table refresh interface changed
And since then there has been a problem
I did a re-link to a data source and added a key
Then I re-linked
The key has been deleted
If I work with Access 2016 there is no problem

MS Office 365 email service provides various opportunities for businesses to standardize the requirement . Moving PST to Exchange Online can be formidable. EdbMails import PST to Office 365 utility does this job easy . You can migrate a particular folder or outlook data files that you want to migrate from a PST file to Office 365 tenant.

The solution supports the migration of PST files to Office 365 including emails with attachments, tasks, notes, contacts, and calendars.

Overview of its features:

Direct PST file migration to Office 365 tenants
No limitations on File Size
Supports Incremental migration. No duplicate items migration on consecutive migration on the same system.
Various filter setting options to migrate the specific data.
Highly intuitive Graphical User Interface.
Supports MS Outlook 2019/2016/2013/2010/2007 and below versions.
‘One time Payment’ - Lifetime license with a free software upgrades
24/7 Technical Support

Conclusion
In this, we discussed “How to Import PST to Office 365 mailbox account?”. You have got a quick solution to migrate Outlook PST file to Office 365. This automated solution easily imports the PST file.

EdbMails simplifies Office 365 Migration by automating the configuration and migration tasks. Effectively transfers the data between two Office 365 tenants. It allows you to migrate all the existing mailboxes, contacts and distribution groups, etc. from one Office 365 tenant to another. Its incremental migration feature avoids duplicates on the target mailbox.

Key Features & Advantages:

• It can perform as a single batch move that includes all of your mailboxes, contacts, and distribution group objects, etc.


• Designed with multithreading which improves migration speed and saves lot of time.


• Only the newly added items are migrated to your target server on consecutive incremental migrations which avoids duplicate items.


• Seamlessly migrate your Public folder data to Office 365 with all sub-folders and folder permissions.


• Easy to use user interface, automatic migration (without any Powershell commands) that reduces your time and resources.


• Supported with easy to use GUI, No Powershell commands involved, which reduces your time and resources.


• Automatically maps the source and target mailboxes for the migration operation. In addition, it allows you to manually change/map the target mailboxes.


• Allows moving the recent data with date filter settings and the user can start working with recent emails. Later the rest can be migrated without any downtime.

MBOX file is supported by 25+ email clients mailboxes such as Gmail, Apple Mail, SeaMonkey, Entourage, Netscape, Eudora & others. But no application exports the mailbox in PST file format. On the other hand, the manual process is useless with a large mailbox plus it does not maintain the folder hierarchy.
So if you want to export direct MBOX to PST format with all mail folder, inline images and attachment than adopt MailsDaddy MBOX to PST Converter. This is the most relevant program that no only migrate MBOX to PST format but also allows user to import MBOX file in Office 365, EML, MSG, HTML, MHTML, Live Exchange & RTF format. The MBOX converter has so many useful features that built on simple GUI interface. The user can also use the demo version first and convert first 20 emails from each mailbox without any cost.

For more information visit: https://www.mailsdaddy.com/mbox-to-pst-converter/

Please increase the size of the footer of the data sheet to make it easier to see and use the record controls. The number of records box should be much bigger to see large record numbers. Also, the search box should be at the top of the datasheet to make it more intuitive to use and be inline with the emphasis Microsoft now gives search in all its applications. I would like to see wrappable columns heading. And the filter button, the add button and a delete and refresh button at the upper right hand part of the datasheet so this consistent with other microsoft programs and obvious for the user to see and work with.

Office 365, 16.0.12730.20144 32-bit.

Select many tables at once in Relationship window - enough so that the list of tables spills over to a second set of columns. Scroll down to bottom of scroll bar, and cannot see the tables lower down. If I then resize the Access Window so it is shorter, I can scroll down and see more tables. And then if I make the Window taller again, I can see the bottom tables. But as soon as I touch the vertical scrollbar, focus shifts to the top again, and the bottom tables are again not showing.

Note that if I make the "Add Tables" area more narrow before I add the tables to the Rel'p window, this problem does not happen. There is now enough space for all the tables to show in one group, rather than spill over to a second set of columns.