Search results

Good for you! - glad this works. As noted, when working with a Access database, and doing things like a dsum() etc. on the data? You REALLY but REALLY want to build a expression that high-speed indexing can be used. Since this "goal" was going to increase the complexity of the expression...

Above is handy, but it's not able to use indexes. So this much depends on how large the table in question is....

Ok, so we want to "sum" a column called "Covers" from a table called "tbl_Net_RestaurantBookings", and pull based on a column in the database called CheckIn. so, the format is thus this: =DSUM("some column to sum","the table to work on", "[ColumnName] = "#some date#") So, you do not want to...

I just installed SSMS22 on my laptop (an older one). It seems to run just fine (loading wise is same, or even somewhat better then SSMS21). To be fair, SSMS (recent editions) is perhaps the slowest loading application I have!!! So, my current laptop? 4ghz, 6 cores, (12 threads), 24 gigs ram...

Thanks for having us, and hosting us here. Looking forward to a great new year, and sharing more fun and things here!!!! A merry Christmas to all, and all the best in the up-coming new year... Regards, Albert D. Kallal (Access MVP 2003-2017) Edmonton, Alberta, Canada

The above is not correct. If you use the before update event, you should be free to modify or do whatever you like. You most certainly do NOT want a me.dirty = false in either of these events........ So, before update triggers - but not yet done. That/this is a excellent place to do some...

Indeed - and the technique I outlined handles that case quite will. And for those not aware of what a "short circuit" means? It means that when you write a "compound" if/then statement, then 2nd (or more) parts of the conditions are NOT evaluated, and are skipped if the first (or previous)...

A great suggesting. In fact, I often try to avoid "nesting" if's too deep, EVEN when a "set" of conditions are requried. In other words, even with a "case" statement not appropriate, I still try to avoid nesting. You can do this by "reversing" the conditions. So, say this: (no need to...

The above is not quite true! If you use a accDB (non complied) application then YES the above is true. However, if you use a compiled accDE, then the above is NOT the case. In fact, any un-handled error will NEVER re-set local or global vars. Hence, we always deploy a accDE. Thus, even...

Yes, it is differrent. Keep in mind, that you suggesting benefits arise that the form now does not have that binding information. However, all you done is move that developer workload to another location - you STILL have to do that work! Remember, I do a LOT of web development work now, so I...

So, how about another example? Well, again, software industry was maturing - but then the smartphone came along!!! And again, huge doors opened up, as many business now wanted and could use some app software (for building inspections, for delivery, for taking on site pictures with quoting...

Actually, no! If you building desktop software, then Access STILL remains a great choice!!! Access is not really fading in terms of what it can do for a given business. The simple matter is that area of the industry has matured, and thus it means LESS investments are going into desktop...

To be fair, in a lot of cases, at least coming from Access land? Often, the issue is not "general" web content, and often the issue is not SEO (search optimizing so Google can find the site). Now, the topic here WAS in regards to building sites with content. As noted, there are a good many...

Well stated.... I only pointed out the above approach (sub forms) as one great approach to building and reusing controls. And as I stated, I have in the past built a form that was driven by a table in which the colluns, their data source etc was defined. So, I've done this in the past. However...

Actually, you can use ADO or DAO. And you can as noted, created the 2 recordsets in code, start a transaction, and then bind 2 recordsets to the the form + sub forms. This "can" be done, and it' been years since I attempted this. And to be fair, I think if you only have one main form, and one...

How amazing - ah, the days of FoxPro, dbase and a few more from those exciting early days of the desktop revolution. So many of us share similar roots as yours in regards to our early beginnings. Really remarkable we talking about something about 25 years old now? (1/4 of a century!!!!). Good...

I think the issue to garner interest is you have to make a really great case as to why this approach is going to benefit the typical Access developer. So, as always, there should be a tangible benefit here, and one that developers see this, and go, gee, I want to do this! I mean, right around...

For any separate processing, since I have really great setup and ability to call vb.net code from vba? Well vb.net supports multiple threads - hence that's the approach I use. Nice, clean, easy, no shell() code, and no .dll registration required..... R Albert

Hum, I not found a issue with simply tossing the form reference out of scope. So, assuming a collection used to hold the multiple instances? Then this should suffice (assuming we use caption). So, then this: Private Sub Form_Close() Call RemoveForm(Me.Caption) End Sub And the...

Actually, if you note many times here? I just use screentogif for my posts. It's quick and simple. As I pointed out, the issue REALLY comes down to HOW you going to know when the user is finished typing. So, for example, in this dropdown, I type in the letter K - and auto complete will match...