User Profile
George_Hepworth
Silver Contributor
Joined 8 years ago
User Widgets
Recent Discussions
Re: Access
We need more context to attempt suggestions for you. Please give us a step by step description of those situations when data is saved. Please also give us a step by step description of those situations when data is not saved. However, start by telling us about the version of Access you are using. We also need to know how long this problem has existed. Did it appear as soon as you created a new database? Now that I think about it, did you create this database yourself or did someone else create it for you? Also describe any errors that occur when you try to save new records. The more details you provide, the better our ability to offer useful suggestions. Thank you.Re: VBA
Thank you for the clarifying screenshots. The middle screenshot does suggest that you are trying to instantiate a template, rather than create a new accdb from scratch. That doesn't follow from the statement that you tried to create a new database, and the 3rd screenshot looks like it would be a newly created database. There's something really wrong. That does indeed indicate a problem with your Access installation, as Richard said. Reinstall Access and see if that clears the problem.Re: VBA
That error is usually the result of corruption in an accdb. You should not see it when trying to create a new database accdb. So, there is something definitely off in the process you are experiencing. Please explain how you go about creating a new file. Are you saying that you start Access, Select File and then New here? Or do you use a different method? Please be as specific as possible. Show us screenshots, if possible, along the way.Re: Adding sub form for a new year
This question sounds a whole lot like this previous question: https://techcommunity.microsoft.com/discussions/access/adding-sub-form-for-a-new-year/4449332 Rather than start off down a parallel path, please confirm whether you are working on the same project as viclea8. The answers being provided in that discussion address the underlying problem, including solid recommendations on how to correct the invalid table design itself.Re: Adding sub form for a new year
I see a some things in this screen shot that make me want to know more about the history of this particular database. First, the image and design of this form remind me what we used to see in the early 2000's, with Access 2003 era databases. Is this one that old? Second, the record selector shows 1 of 1843. I assume that would refer to the number of members, which is rather small for a database as old as this appears to be. Third, the implication of having tabs for different years of dues is that the underlying design might not be appropriate. Does this database have different tables for each year's dues, in addition to the subforms? As Tom said, all those subforms is going to lead to their own problems, and if there are also multiple tables, it's even more sketchy. All in all, the impression created by the screen shot and desription is that this is an older database in need of tender loving care to make it more viable. Show us, please, the table relationships in this database.Re: No longer able to edit/enter into Access Query
In order to offer suggestions, we need more information about the query. Start by showing us the SQL from the query. Open it in SQL view. Copy the SQL from it and paste it here. Explain what the query is supposed to do. What is its purpose? How do you need to use it? Also, show us some sample data from the table. That helps us understand the process. Thank you for providing enough information to be able to offer assistance.Re: SSMA For Access not recognising DateTime/Extended fields
I have the same version. I opened an issue for this missing datatype in the SSMA GitHub, using the Feedback option under Help in SSMA. https://github.com/microsoft/SSMA/issues/20 Perhaps you can add a comment documenting the hurdles you face because of this ommission. I can see how this will become an even bigger issue as more people adopt the DateTimeExtended option.Re: MS Access Database Decommissioning
Access 2024 is the latest standalone version of MS Access. So if you want the latest version, yes. However, it is no longer part of MS Office except in one version. Otherwise it is sold as a standalone product. https://www.microsoft.com/en-us/microsoft-365/p/access/CFQ7TTC0PD0B https://www.microsoft.com/en-us/microsoft-365/blog/2024/09/30/office-2024-for-consumers-available-october-1/ You may also purchase a license for a version of M365 that includes Access. Some do include Access, some don't. https://www.microsoft.com/en-us/microsoft-365/business/compare-all-microsoft-365-business-products-b?ef_id=_k_82588f2ea6a615bc268ee7b2481e87d6_k_&OCID=AIDcmmq8c1jdfb_SEM__k_82588f2ea6a615bc268ee7b2481e87d6kRe: SSMA For Access not recognising DateTime/Extended fields
I see that you did provide a repro accdb in the other post. There is no way to add the new, previously defined datatype DateTimeExtended, in SSMA. Maybe there's another workaround, but it sure does look like converting the datatype in Access is the way it will need to be done to support migration, even though SQL Server supports DateTime(2).Re: MS Access Database Decommissioning
Do not worry about it. Access version 2019 is NOT going to be decommissioned. Access 2019 will go out of Support. Those are two different things. End of Support means that no updates will be pushed out for that version and Microsoft will no longer provide customer support. Access 2019 itself will continue to function just as it has for the last 6 years. Nothing changes except you can't call Microsoft for help if you encounter problems and there will be no new updates for it. It's "frozen in time" as it were. Also, as I tried to explain once before, the reference to the Access 2007-2019 file format is NOT relevant to this particular discussion about the life cycle for any given version of Access in any event. File format refers to the fact that Microsoft changed the internal file format for Access databases from .mdb to .accdb in the 2007 version and has kept it essentially the same since. It's not worth going into the significant internal differences here. Just understand that the file format of the accdb is not the same thing as the version of the Access executable file, MSAccesse.exe. MS stopped updating that file format reference in 2019 because the file format itself -- the .accdb file format -- hasn't changed significantly internally. It's also now the same in M365 and will continue to be the same. Here's the problem. You are conflating the end of support for the Access application itself, i.e. the MSAccess.exe for Access 2019, with the file format of accdb files created in any version of Access. To reiterate. End of Support means no further updates or bug fixes for the Access 2019 version of MSAccess.exe and no more customer support service for it. Nothing more than that. ALL installed instances of Access 2019 will continue to function as they have done. As a matter of fact, people around the world are still running instances of Access 2003, 2007, 2010, etc., etc. even though none of them are supported any longer. All that means is "No new updates. No Bug fixes. No free customer support calls." Your accdb files will continue to function as they do now and do so under M365 versions of Access.Re: MS Access Database Decommissioning
No, the accdb format is the same. Newer versions can introduce new features. That doesn't impact features in accdbs created with older versions. Deprecation of features can be a different story, but between 2016 and 2019, that was not a problem. However, now that you mention Access 2019, you've raised another issue. Access 2019 reaches End of Support in October. https://learn.microsoft.com/en-us/lifecycle/products/access-2019?branch=live That means you should be moving to Access 2021 or 2024, not 2019. Or to the perpetual license version in M365.Re: MS Access Database Decommissioning
It's probably good to keep in mind that backwards compatibility is an important consideration for Microsoft products. You can even run mdb files created back in 2003/2004 under M365 Access. Since you are now using this database with your current M365 installation, it's quite likely that you have either have 32 bit Access installed, or that nothing in the database uses 32 bit only features. What matters in that regard, would be if your organization did switch to 64 bit Office in the future and you'd have to deal with any issues at that point. Making an accdb 64 bit compatible is not difficult, although it could be time consuming.Re: MS Access Database Decommissioning
On one level, it's impossible to suggest when this particular database application might need to be modified because we have no visibility to the way it's designed, built and used. That's what determines its usability in any given version of Access. However, in a more general sense, we can comment on things that matter. It is in the Access 2007-2016 file format, meaning it's an accdb created sometime in the last 18 years. We'd need to know which version of Access was used to create, 2007, 2010, 2013, 2016, 2019, 2021, or 365, to know more than that. Moreover, we'd need to know what features were used in creating it, such as Modern Charts, or Large Number Support, and so on. The more recently it was created, the higher the likelihood it could contain newer features. On the other hand, a few features have been deprecated over the years. You would already know about that because you apparently are currently using it. Given that it is currently in use, I speculate that it doesn't include any now deprecated features. It's fine, and should still be fine in the foreseeable future. Ultimately, it's safe to say that it's as "modern" as any existing Access database application and in no need of updating or modification for that reason alone. You might want to update or modify it if your organization's needs have changed, but that's a different matter. There may be additional considerations, about which you would need to provide details. For example, if this accdb uses 32 bit specific components or code, you would need to modify it should you switch to 64 bit Access at some point in the future. But until and unless you do that, there's little or nothing to update. And finally, the bottom-line test: Try to run the accdb as-is in the latest version of Access, either Access 365 if you have the subscription version, or most likely Access 2021 if you have the perpetual license version. (Your organization may have Access 2024 if you have deployed that version.) If there are problems, you will know you need to update. If there are no problems, it's good to go.Re: ver2507 bug
It appears that this problem with the LTM could be related to another reported bug from a couple of days ago. It indicates a more widespread problem. Please give us more details about the specific error message and the specific steps you followed that led to the error. This has already been reported to the Microsoft Access team, and we'll add this additional information as soon as you can provide those details. We need to confirm it is a related issue. Thank you. You can try rolling back the most recent Office Update, which has been successful for another user who reported a similar problem. This article explains how to do that. Note that this is not a downgrade of Office, just a rollback of a recent update.
