User Profile
George_Hepworth
Silver Contributor
Joined 8 years ago
User Widgets
Recent Discussions
Re: Access Query Finding Old/Deleted Data
What does it mean to say that you uploaded a new version of the "Medical Department and Chair" table to override the existing version? Uploaded to where? Again, I am not sure that you actually replaced the table as it is used in the current database. To repeat, please describe, step-by-step how you did that. It does appear that you have a split database, with a Front End (FE) accdb contains the interface and logic objects and a Back End (BE) accdb containing only tables. That's good. The problem appears to be that the link from the FE to the table in the BE was not changed when you "uploaded" a new version of that table to the BE. That implies a) the new table is there in the BE in addition to the old table and that b) the process did not include changing the link to that table. That's why I want to see a screenshot of the Navigation Pane showing all of the tables, please.Re: Impossible d'installer Windows 10 22h2
Unfortunately, you posted your Windows Installation question in a forum for support of the MS Access application, which is used to create relational databases. Please repost your question in a forum that supports Windows Installation to get the attention of people who can provide pertinent suggestions.Re: Access Query Finding Old/Deleted Data
Please explain what you mean by "replacing outdated tables". Please describe, step-by-step how you did that. Queries can only retrieve data from tables when the tables are available, so that old data does exist and that implies the original tables are still available, not replaced. It would be very helpful to see a screenshot of your navigation pane showing ALL of the tables in the accdb. Thank you for helping us help you.Re: Access Not Responding
Unfortunately, it's very hard to guess what the problem in this particular situation could be, based only on knowing that Access stops responding. In order to help us help you, provide a step-by-step description of what you have to do to produce the error. Include information about the version of Access and about the version of SQL Server involved. The more detail you provide, the better the chances are that someone will recognize potential problems in your environment and procedures.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.
