Search results

Well, things have vast improved over the years. So, while at one time, say a VPN between two locations, and running a split Access database? Was not that practical. Now, well, actually it is! However, if the VPN was being used say by “at home” workers? Then that falls down, since it not all...

Ok, now that changes things a wee bit, but again, with hardware where it stands? Well, since the network bottleneck is gone? Well, as long as one has a multi-core CPU. And these days, that's probably a min of 6 threads, and more CPU's? Then that will suffice, and once again, throwing more...

The problem is that if you do what I done for years? That is build the relationship using the UI/diagram tool? You THEN set/create the index after? (which is what most people probably do....) The diagram does not update - so, you don't notice this effect. I ONLY noticed this, because I was...

Ok, I HAVE to do a follow up post! One of the things I love by helping and posting to the community here? Well, you find out VERY interesting things! While I made a long winded post about how SSMS does not really tell you the difference between a one to one, and one to many? I am WRONG!!! -...

If just looking to add content, information, then some type of CMS as WordPress is a really great way to go. But, if you looking to build say forms, code and an applicaiton? (like moving some Access application to the web)? Then of course a different road is required....... And don't worry -...

LOL!!!! - don't get me started on that issue! (as a FYI: I actually was one of the few Access developers that supported this amazing feature!!!). R Albert

Actually, the answer is a round about way is kind of funny! SSMS designer lets you setup relationships, but it actually NEVER calls them anything! (so, no names like “one to many” or “one to one” etc. is ever used, nor displayed). On the other hand? I don’t consider that a many to many...

If you 100% local, no network involved? The having a really great and fast hard drive is the ticket. In most cases (at least these days), Access is not limited by CPU cycles - we have boatloads of those. Hence, in near all cases, it's not CPU, but WHEN access has to use/get/grab external...

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...