You (and anyone else of course) should find all the details from the link, but no. It's indeed not an online event.
Exclusively IRL ;-)
User Profile
Collapse
-
👍 1 -
UK Access User Group - The “App-in-a-day” conference – May 2026
The IBIS Birmingham
New Street
21 Ladywell Walk
Birmingham
A conference with a difference, featuring a top panel of speakers collaborating on building a single application!
Armen Stein, Anders Ebro, Kevin Bell, Julian Baker and more will present and make this a great day!
More details - See below.
Get Tickets £58.60 – £160.00 25 tickets leftA conference with a difference, featuring a top panel of speakers collaborating on building a single application! Armen Stein, Anders Ebro, Kevin Bell, Julian Baker and more will present and make this a great day!Last edited by NeoPa; May 12 '26, 11:31 AM. -
I wouldn't suggest the work-around I suggested was simple or straightforward Peter, in fact I specifically called out none was.
However, I should have thought of the wrapper function idea. That actually is relatively straightforward to be fair (& quite common - I just had a brain-lapse).
I guess I tend not to use the TVs mainly because I was working without them for so long & had solutions based on not requiring...Leave a comment:
-
None that are simple Petrol :-(
I typically avoid TempVars generally, but if you had a table defined to store a single record & set Fields in that table (just the one in this case) to match where you need to inject your data then you could link to that table to get the value you require.
So, your recent SQL would look something like this instead :
...Code:SELECT [WalkNumber] , [StartDate] FROM [Walks] WHERELeave a comment:
-
That's a deeper question.
There are issues with repeatedly building onCurrentDb()as each reference is to the result of a function that returns a DAO.Database object. No two calls toCurrentDb()ever return the same object. It's always a copy of the database with updatedCollections.
That points to where using a cached copy in a DAO.Database object can leave you with staleCollections if you don't call.Refresh()where necessary. ...Leave a comment:
-
My best guess is that it's related to using `CurrentDb()` directly - which is highly contra-indicated.
Try instead :
This only helps if that's your problem, & I don't know that. However, I see nothing else here so hopefully that's it & gets fixed.Code:Dim dbMy As DAO.Database Set dbMy As CurrentDb() Set rsLOI2 = dbMy.OpenRecordset("qry_LOI2", dbOpenDynaset)Leave a comment:
-
All good advice I would say :-)
There is a slight difference between what you seem to be doing & the natural behaviour of of the ComboBox Control anyway. You're doing a search where the typed content can appear anywhere, while the default behaviour merely matches that text at the start of an entry. Maybe important, but maybe not. Only you can know.
You can already see though, that every time you set the properties...Leave a comment:
-
-
Well, I have to say I'm flattered to think there may be people who assume I can translate numericalVarTypevalues into their textual meanings off the top of my head :-D
Unfortunately I suspect that too few parameters is simply telling you that it's been led to expect some value or other that isn't present. It's general & non-specific. It almost always requires that you examine the SQL, or sometimes even other details of a QueryDef...Leave a comment:
-
A couple of points, well I suppose three really :- I have no idea why the dbForwardOnly would have any such affect as you explain.
- When displaying the value of TempVars!commun itycode be sure to do it in the code before it crashes so that we get to see the value you intended.
- The value of 'BS' tells us (for the first time) that it's a string value rather than a numeric one. This is often important when dealing with SQL code, though as you'll
Last edited by NeoPa; Jan 6 '26, 03:21 PM.Leave a comment:
-
Why not see what happens when you simply try to open the QueryDef ("TestQuery" )?
Obviously, show the value in the Immediate Pane first with :
?TempVars!commu nitycodeLeave a comment:
-
Hi there Petrol.
The Outlook.MailIte m object has various properties that pertain to who sent the email (Sender, SenderEmailAddr ess, SenderEmailType , SenderName, SendUsingAccoun t & SentOnBehalfOfN ame) which cover that area. You could also look at the ReplyRecipients collection property for whom the reply should be addressed to automatically.
Essentially, theOutlook.MailIte mobject needs to be set up with this information...- Selected Answer
Leave a comment:
-
Interesting. Maybe setting it to the same value that it already has doesn't get recognised as an update - even when your code sets the.Valueproperty of a bound Control.Leave a comment:
-
It seems you've already found the solution Petrol.
However, to your point about a message going out to notify the user, let's deal with that. There are two main ways to handle that :- Probably a bit more common is that you move the code that displays the message into the
AfterUpdate()section of your code after theFixPhoneNum()procedure has completed. It's main drawback is that it might need to be repeated in every place you update
Last edited by NeoPa; Nov 18 '25, 12:26 AM.Leave a comment:
- Probably a bit more common is that you move the code that displays the message into the
-
Hi Petrol.
Without answering directly for now, the usual approach for checking user input is to include it in the BeforeUpdate Event Handler
(txtHome_phone_B eforeUpdate(Can cel As Integer)). Notice that has aCancelparameter.
If/whenCancelis set toTRUEthen the update doesn't proceed - which is different from your logic where it updates to the wrong value before being updated again to the text "Invalid"....Last edited by NeoPa; Nov 16 '25, 04:15 PM.Leave a comment:
-
I should add that when you use something else in place of your originalStartup()code it's important that you do *NOT* include the oldStartup()in there with it - even if it isn't invoked from anywhere. It must be replaced completely otherwise it's still included in the file that you're testing.Leave a comment:
-
Let's try this again. When I say test the issue again, I'm referring to the issue where it crashes after a Compact & Repair.
So, my question is referring to that. From the answer you gave I assume that means that 'the issue' is still with the database, even after removing the AutoExec macro.
So, if you create a brand new database again & give it a dummy AutoExec (that does little but exists & gets run), you can...Leave a comment:
-
I just revisited your OP (mainly in order to fix the extra spaces) & saw that you'd already tried all that (pretty much). I'd forgotten those details before my reply, so apologies for that.
If you take the existing database that has the problems, & remove the Autoexec macro completely, does it return fundamentally to a working form - or do the problem(s) persist?Leave a comment:
-
While all sorts of special characters are indeed allowed by Access in the names of Forms & Reports, most experienced developers & experts will advise caution with the use of any sort of punctuation characters as these can cause confusion when referring to the items outside of VBA - as well as having a tendency to confuse when reading the VBA. You're absolutely correct to conclude that this should not be any part of the problems you're experiencing...- Selected Answer
Leave a comment:
-
MVPs must, if they feel any responsibility at all, be far more considered before making their opinions as to how things should work known to the A-Team.
Experience (should have) taught us by now that, just because the reasoning for something isn't clear & obvious to us, doesn't mean that they got it wrong. On most occasions when we bring up anomalies we are privileged to hear the reasoning that they were working to which is often...Leave a comment:
No activity results to display
Show More
Leave a comment: