Hi Larry,

First of all, I sincerely apologize for the delayed response. We've been experiencing an unusually high number of tickets, and I'm truly sorry it has taken longer than usual to get back to you. Your patience is greatly appreciated.

You are right — I was able to reproduce the issue, and it appears to be a new bug on our end.
I believe this was working properly in some previous versions.

As you described: for example, if we switch any Manual table from Standard View to Excel-Like View, save the changes, then navigate elsewhere and return to Browse Tables and reopen the table, it opens again in Standard View instead of the saved Excel-Like View.

Here is a short video demonstration showing how we reproduced it on both LocalHost and our Sandbox environment.

We passed this to our QA Team, who will coordinate with our developers to isolate and fix the issue as soon as possible.

We don’t have an exact ETA yet, but please keep an eye on our wpDataTables changelog — all implemented bug fixes are listed there with each update.

If the developers create a hotfix between official updates, I will make sure to send it to you directly.

Thank you again for your understanding.

Hi Larry,

Thank you for your patience while we checked this with our development team.

I’d like to clarify that the behavior you're experiencing is actually the default one. My apologies, it seemed to me this was different before, but that is not the case.

The table will always load in the Standard Editor View when you return to the backend—this has been the standard behavior from the beginning, and I apologize for any confusion caused earlier.

If you’d like your table to display in Excel-like View on the front-end, you can achieve this by adding the parameter table_view=excel to your table shortcode, or by selecting the Excel-like view option when using one of our built-in page builder integrations.
You can find more details in our documentation here:
👉 Excel-Like Editor in wpDataTables

Since this current behavior is by default, we can’t treat it as a bug or issue at this time. That said, we completely understand how a preference or toggle to remember the last used editor could improve the experience.

If you'd like to see this feature in a future update, we encourage you to submit it as a feature request to our development team.

Please feel free to search on our suggestions page, 

 to see if someone may be already suggested this feature. If you can't see it, feel free to add your suggestion there,  and as more people vote, the feature will move higher on the priority list.

You can certainly follow our changeLog page if you'd like ( it is also available in the plugin dashboard), where we state any changes/new features/bug fixes during updates;

and our newsletter, so you're informed about new features, bug fixes, freebies, etc.