One thing you could think about is whether you can always get to a consistent state. If you trap Form1's Unload event, you can set it to never close using Cancel = True and always set it to hide unless certain conditions are met. From that, you may be able to work a solution.
To do a proper search function, the most effective ways is to create an inverted index of the items you wish to search on and use the results of the search on this to link back to the items. It's pretty standard stuff which you should be able to find on Google.
Re: "Because we are a 24/7 operation and the information in the database is CRITICAL"
I'd stop worrying about a 55 second time delay and worry about moving the data to an enterprise quality database. SQL Server Express has these qualities and is free.
C
As long as the convention is understood, there's no reason to need to use restrictive access modifiers on the concrete types."
But humans are involved......
Re: Plan, Do, Check, Learn.
More commonly Plan Do Check Act, the classic Deming quality cycle.
Re:
1. First, you have to understand the problem.
2. After understanding, then make a plan.
3. Carry out the plan and test.
4. Look back on your work. How could it be better...
What line of code is throwing the error?
A quick Google search indicates plenty of people with similar problems when using the [Forms]![frm...] syntax, many of which are resolved using the Me. syntax
C
Of course the user should not interfere with the technical solution.
But what should be reasons to follow or NOT follow the technical solution the user suggests?? "
I think that summarises your problem nicely. You're doing things that you believe are right but have no rationale for doing so...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.