Search results

Sure, you could do this, but you talking about editing "one" record. If we were to limit this discussion to not a form + sub form (which by nature mean repeating reocrds in the sub form)? Sure, then FoxPro could be aruged to handle this issue. But, on the other hand, EVEN in Accesss, and EVEN...

Ok, and for my "narrative" here? My narrative was not so much about having a single "save" button for the form + subform, but ONLY when you have or want a transaction type of save, or NOT to allow the save. So, my example was the sub form in which several rows are added but the total MUST match...

For a lot of us here, VB, then VB.net, and all the while we kept using VBA (in Access). Today, Python is super popular - much like VB was back when so many of us started our journey into computers. In many ways, Python is the "go to" choice and language for oh so many today..... Regardless, a...

Ok, I'm going to give my 2 cents on this one. It would be REALLY cool and really nice if we could wrap (with ease) a main form + sub form editing into one simple transaction. After all, from a user's point of view, when editing say a invoice (and the classic sub form of invoice details)? To...

Don't worry! - you simply wanted a non polling event - other issues are not your goal here! I was just pointing out that others here have other ideas and are going on tangents - one's you not interested in!!! So, while I explained others (even me) have other ideas and suggesting's here? They...

Well, you have this position on this matter - but people here do not! (and that’s the problem here!) We here have not agreed to that position of yours! It may well be YOUR position on this matter, but it is not (yet) OUR positions here on this matter. So, at this point in time, this is not a...

Not really, but on the other hand? If you remove "poor" design decisions made, then 9 out of 10 times, you not experience any "not responding" messages. In this case, the developer gave no thought as to why and when to use "on-open" vs "on-load". A basic mistake, and for me, I would have...

Fair enough!! - and I VERY much like that you admit that what you have is less then ideal..... However, that's life! - You certainly can "improve things" - always a great idea! Regardless of the above, placing a doEvents between each dlookup will fix the freezing, and the controls will thus...

Well, I can say one suggesting: Use bootstrap when possible. But why do I suggest this? Well, imagine that you hired a REALLY great team of graphic designers. (and if you have access to that graphic design department? I STRONG suggest that after you have some basic layouts, then get them to...

yes, give my suggesting a try - it should then update each dlookup() as they complete. Funny how one "little" tid bit of information (the on-open event) gives rise to a solution here. I'm actually quite confident this will work for you.... You not need a repaint - the doEvents should suffice...

Ah, very well then! Ok, so do you have code in which a whole bunch of dlookups() are triggred by VBA then? If yes, then I suggest several things: First up, move such code to the on load event. On open is too soon, and the form display (and the display thread) has NOT YET been started by...

Right, as I explained, calling ACE/JET code means the code waits - just like if you called a VBA sub routine. It's blocking, and Access will have to simply wait until that dlookup is done - it's not ANY different then you having to wait for a VBA routine to complete. DoEvents() will thus not...

Well, at some fundamental level, actually it does matter. Since if it did not, then you would not be asking this question, would you? In other words, a big reason exists for this goal – and that goal is 100% centered on some data being changed. As I stated, if it did not matter, then you would...

I think the REAL question is what do you want to occur when that data changes? And who, and how and why did that data get changed? So, you could I suppose setup a database trigger, and if that change occurs, then "more" or additional data processing could occur, including that of say a email...

True, but you still free to make asynchronous calls - even with CreateObject(). I mean, if you want to call a long running SQL stored procedure? You can make that call as synchronous, and the VBA code will wait. Or you CAN make that call as asynchronous - the code will NOT wait!!! So, no...

Well, the MSXML object does not support "sunk" events in VBA, but you CAN STILL call the MSXML library code as "asynchronous" I suggest this code pattern for a 10 second timeout, and if it takes longer then 10 seconds, then you bail out - and do so without a freezing UI. Sub Test() Dim...

You are correct, but the REAL issue is in fact the data engine. So, think of a old 8 bit game, or even a PC game back in the DOS days. You had multiple things moving on the screen, you could use your arrow keys, and "everything" seems to continue updating. No UI lockup's, is there? Access has...

Well, first of all, if you do a lot of stuff, then the Access UI will lock up. There ARE some threads, and don't confuse that of "threading" models vs that of multiple processor tasks (often the term task and thread are mumbo jumbo up here). >So then in Access, how do you fork/exec a new...

I suppose it depends on the GUI + the process....... Linux land often is working with non GUI, and when the GUI "does" try to do something, then VERY often it's another separate process being kicked off. And Linux does not have a single GUI manager like windows. So, there's no real "nanny"...

Just re-set (re-apply) the path name to the control. Works for me. eg: Image1.Picture = Image1.Picture R Albert