Search results

In the code line you posted it has SAddresListName with one s in address. Has that been changed somehow?

Yes, you don't want unhandled errors but you might need to react differently depending on the actual error, and that is much more difficult to handle, and identify report and resolve the true cause.

Error handling is not as simple as merely making sure that there are no unhandled errors. Some errors might indicate a dangerous/catastrophic problem that can't be simply recovered from.

You aren't using a laptop and accidentally moving the mouse with the touch pad, are you? Also mouse behaviour gets erratic as battery power wears out. I get those issues from time to time, although I don't get forms being corrupted without realising it's happening.

What on earth do you mean by the above? Are you trying to say you have a master table for persons that appear in other tables? I think I would rather have the duplication by having the same person appear in more than one table, without the master table at all.

The thing is, do you want to remove an item from a combo box, or remove the item from the database altogether? These are different things, solved in different ways.

Am I not right in thinking that merely adding ptrsafe does not guarantee that the code actually works correctly in the different environment? It may depend on what the function actually does.

It goes back to consideration of your processes. When you say "update an invoice details", or "update notes on a job". Well I imagine the notes should be in a notes table, not in the jobs table. The invoice details should be in an invoice details table not in the job table If you normalise...

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.