Philipp Stiefel
My feedback
-
1 vote4 comments · Access (Desktop Application) » Automating Tasks · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment -
31 votes
An error occurred while saving the comment Philipp Stiefel
commented
I think this suggestion needs clarification. You should specify exactly which OCXs/DLLs you mean.
-
5 votes
An error occurred while saving the comment Philipp Stiefel
commented
We ran into the very same problem with images no longer displaying on the report. For us the problem started already after less than 10 images were displayed! - We were able to build a workaround for the problem by creating small thumbnails of the images at runtime before displaying them in the report.
-
299 votes
Thank you for your feedback. This work is in scope to be completed within the next few months. The Access team appreciates your patience in advance.
An error occurred while saving the comment Philipp Stiefel
commented
Access Applications that show multiple forms, each containing several subforms, side by side run into out-of-memory-errors very quickly. This is a completely reproducible issue. Currently the only mitigation is to limit the number of open forms. To reliably prevent the issue a max limit of no more than 5(!) forms may be required.
Philipp Stiefel
supported this idea
·
-
217 votesPhilipp Stiefel
supported this idea
·
-
37 votes
An error occurred while saving the comment Philipp Stiefel
commented
@Nick76: SaveAsText/LoadFromText usually do work across different versions. Old Access versions (pre 2007) used to be picky about the Version and Checksum properties in the file.
In general, low version to higher version should work, high version to lower version might fail due to new features used in the object that are not supported in the earlier version.
If your problems persist, I suggest you post to any QA-Forum to get this sorted. This is not the place for support discussions.Philipp Stiefel
supported this idea
·
An error occurred while saving the comment Philipp Stiefel
commented
Your understanding of OASIS-SVN and Ivercy using these methods is correct. (I'm the owner of Ivercy)
-
314 votes
Thank you for your feedback.
In terms of setting SQL Server as the default database format, that is currently not in scope for the Access product. We have provided and will continue to provide efficient methods to integrate your Access data with SQL server, and the team will continue to develop more features that streamline the data migration experience (see https://support.office.com/en-us/article/migrate-an-access-database-to-sql-server-7bac0438-498a-4f53-b17b-cc22fc42c979)
However, the ACE database engine has and will continue to be Access’s central data storage unit.
There are new features coming soon that will improve the Access: SQL experience, and we are excited to share this news. Please stay tuned! :)
Philipp Stiefel
supported this idea
·
-
239 votes
Thank you for the feedback. These requests have been an ongoing discussion with the team, both internally and externally. Especially with our continuously increased focus on establishing a stronger Access-SQL experience, we do plan to have some requests on this work looked further into within the next year. We will keep you posted with specific feature designs in scope as well as timelines. In the interim, you can continue checking our public roadmap for feature updates.
Philipp Stiefel
supported this idea
·
-
9 votesPhilipp Stiefel
supported this idea
·
-
32 votesPhilipp Stiefel
supported this idea
·
-
233 votes
The Access team is adjusting our status for this request – we are planning to embed the Monaco Editor (support for SQL Editor improvements) into Access, to be released within the next semester (first half of 2021), which will provide capabilities such as syntax highlighting, IntelliSense, SQL comments, and more. We are excited to have this capability released by next year, and we appreciate the energy and enthusiasm on this feature request. We still have a long ways to go to improve our experience with SQL, so please stay tuned as we execute on this objective!
Thanks,
Ebo [MSFT[Philipp Stiefel
supported this idea
·
-
21 votesPhilipp Stiefel
shared this idea
·
GetOption/SetOption are for Access Options applying to the Access installation itself. The Startup Form is a database dependent property. It should *not* be set by GetOption/SetOption.
The approach outlined by Anders with DB.Properties is the right one.