Search results

Did someone say they had expertise in UK tax. I have a query relating to IHT changes today.

Yes, but your activities don't necessarily cause problems. Estimators entering different orders/quotes isn't an issue, as the optimistic process doesn't lock a block of records, or indeed any records.. It just re-reads the single record to see if a different user changed it while you were doing...

If you don't set the trusted flag, you get asked whether you want to open the database each time. I imagine this is there to prevent malware databases opening without approval.

Having no locks doesn't mean it's a wild west free for all. This all works on the basis that you can have multiple users reading a record. The problem occurs when someone writes a record. What no locks (optimistic locking) means is that access assumes that a write will be successful, but...

Every day is a learning day. It's a shame it can sometimes take a while to understand the real reason for a problem.

But this is completely different to choosing an inefficient sorting algorithm. I don't believe it is of any use to consider the question "what will we do if the problem is too complicated for MS Access". We are doing that continually in a microcosm. Occasional we get queries that are too large...

No 7. Is what I said. The design commissioners and specifiers may not understand the business needs well enough, and may not understand the development possibilities that are available to produce an optimal (or tending to optimal) solution. The developers may not understand the real requirements.

Well you can give him what looks like he asked for, but design in it a proper normalised way, so that when the client wants more complications you have a framework that enables the growth.

You are probably best having code in each controls event to highlight the control in the way you want, and deactivate the previous control. it won't do it the way you would like in a continuous form though.

It's only of academic interest because I expect a vanishingly small number of us have ever been involved in projects that conceivably could get big enough to challenge the limits of access, and no doubt we would have a strategy to deal with it if it became necessary, or more likely well before...

You can treat time as text, and check that the string includes a colon. Force users to enter military time, and reject badly formed spreadsheets. Otherwise you will end up treating 0.75 as 18hours, or 6:00pm, and there's no way to know if that's what was meant.

It's hard to distinguish between a 1 and a lowercase l. Sometimes the errors get picked up are illusory as well. it's easy to get coding constructs that pass the syntax tests but don't run in the way you wanted.

Having said that, you also have to realise that users are likely to be conditioned by their previous experience and won't necessarily recognize and value all improvements at first sight. The real problem is that developers understand development, but don't understand business practice, and the...

I still don't believe that any database needs to grow month after month, unless it is caused by normalisation issues, and duplication of processes. Therefore the ever expanding project could be dealt differently without needing to add new forms perpetually. Additionally, as already...

I'm not sure but you might also need spaces before and after the equals sign in these expressions. I probably add spaces in SQL expressions where I don't need them, but I know for sure there are some places where you do need to have them.

And you academically discussing a notional super sized project doesn't mean you really have one. I still don't understand why every month you need to redesign the project, unless it's not been well designed in the first place. That's why I would rather not discuss hypotheticals.

@amorosik I really think you are talking about an academic/esoteric situation that is most likely unable to ever arise. ie. Can you comprehend a system that is too big for access development? I just can't personally. I have systems that need more space for millions of records, but that's a...

Maybe I'm wrong. What I thought was it's possible to have one mdb that will run correctly in either bitness of access, but it won't compile to an mde that will do the same. That's what I meant anyway.

@Misionero I don't think you are getting this. This is two 1 to many relationships. Workers table Projects table WorkedBy table Workers 1 --- N WorkedBy N ---1 project. There is NO direct relationship between the workers table and the projects table. (Well, there's a M:N correspondence, but...

And the real question is .. why would you have a project that is never finished? Why would it need to grow continuously? Why can't you design a form or a query that works correctly in both 2024, and also runs in 2025 without needing to add a new form for 2025. I assume that's the sort of problem...