As suggested by xavier, seems to me the switch option is the way to go since this is in a query
Expr1: Format([fld],Switch([fld]=0,"-",[fld]>-1 And [fld]<1,"0.0",True,"#"))
important to get the order of testing correct
One of my clients uses a bank which changed to a new system which apparently had been ‘extensively tested’ before being released. Nothing worked reliably from being able to log in to processing payments to downloading transactions.
Even the 100 page manual you get pointed to has errors such as...
My bad - but see you worked it out. To sort in date order, you would need to specify year before month e.g. yyyy-mm
You don’t need to display the sort column
Suggest you step through the code to check what actually happens is what you expect to happen
Looks to me like you have an exit sub before clearing the controls
You don’t really need an end date - it will be null for the current name and one day less that the next start date for previous names and easily calculated if ever required.
End dates are really only required for data that can end - such as a contract
Create an ‘alias’ table as a child to your main table. I have a similar situation where a club member has different member numbers depending on the activities they partake in. This comes from an online booking system over which I have no control
God decides it’s finally time to send Jesus back to Earth.
*poof* All of a sudden, Jesus finds himself on the side of a road in the middle of rural America. He sticks out his thumb for a ride and before long a man in a truck stops to give him a lift.
Not revealing his true identity, Jesus thanks...
So far as I can see the OP hasn’t said it’s a requirement, but if it is, you can pass the recordset to ado although you would lose the ability to sort/filter unless you write your own shortcut menus
You can do this with a form -see this link
https://www.access-programmers.co.uk/forums/threads/making-a-form-look-like-a-report.326715/
Think it is the third example