Cannot see data after year change

[Ericsp]

Hi Guys


The Test DB I uploaded is identical to the normal with all but 1 record removed. When run on my PC the effect is the same as the normal DB ie when I try to update or add a record the form just shows No Records. I seldom use most of the other options. If I change the PC date to 31/12/2021 then all appears well. I was given this DB some 15 years ago when the author passed away and I only act as a user and have little technical knowledge. Equally all of the members that I would normally be able to ask are aviation knowledgeable and not IT. My PC is an HP desktop running Windows 10 with all updates loaded as they are made available.
Eric

[Micron]

Did you ensure that you could replicate the behaviour in the db you posted when it has just one record? I can't see how I can help with that when things like queries will only work with related data in the tables that are part of the query. In other words, date issue or no, we'll get no records anyway. Kind of hard to help in that case.

[Gicu]

Sorry for the late arrival, please have a look at the updated file. Your problem was caused by the missing records in the DrawYearsConversion table which stopped at 25. I have added a few more so now the MemberDraw(Query)1 returns the record and therefore the equijoin to the table Members also returns the record (in the Current Members (Query) query which is the record source for the form).

There are many issues with your db (not normalized, bad naming, use of lookup fields - I removed the lookup on the membership Id in the Members table), but as you seem to have used successfully for your purposes for many years lets hope adding those records in the DrawYearsConversion table will make it work for you.

Cheers,

[Ericsp]

Hi Guys
Many, many thanks for all the help you have given me - it really is very much appreciated.
Special thanks to Mike60smart for taking so much time. Your help and skill have been invaluable to me

Suffice to say that the DB now seems to have been restored to its former working position.

[Welshgasman]

You need to understand what caused it
I have no idea what that table is meant to represent

[Gicu]

Congrats for making the db work again, by changing the record source of the form to just the Members table as in Mike's sample was the right move, you should also change the recordset type back to Dynaset as the inconsistent updates are no longer needed.

Cheers,

[Welshgasman]

I must admit, I would have left it as it was? Especially as you found the issue?
Who knows why it was done that way?, as the db looks reasonably decent at first glance?
Who knows what side effect can happen, if the form is just based on members?

[Gicu]

I agree, that was why I said that if it worked for so many years it would probably still be OK. Not sure what exactly the OP did, I assume he went with Mike's changes which would probably be an improvement in the overall design but might impact other parts.

Cheers,

[Welshgasman]

Well I would go with your changes.
Only a few records to add?, much safer in my mind.