Search results

Not the ones I build. We made the decision not to do this (for many reasons) and I've always felt it was the right decision. Having separate backends/deployments per customer seems to be the generally accepted practice by most others who are building SaaS apps as well. Set yourself up with a...

At one point one of the early O365 installs used to default to it (not sure if they still do). We had a self-IT'd client whose whole office wound up with it because of that - I had to show him how to explicitly select the 32bit. Maybe 3-4 years ago? (that was my final driving factor to get on...

64bit makes it more difficult to use a lot of the older ActiveX controls. A few years back we got more or less pushed into supporting it because clients were installing the default from the new CTR installations, which was 64 (they didn't know any better). Eventually we got the majority of the...

Hi Stuart - I'm not a guru when it comes to pivot statements, but my guess would be that you have your unexpected zeros because of this line: TRANSFORM Nz(Count([Audit initiation date]),0) AS [New Audits] The Nz() function is a "NullToZero" function, which takes your count of dates, and if...

I've used it in a number of scenarios. Inventory tracking was one. We have a number of different inventory types for a manufacturing facility (purchased goods, manufactured goods, consumables), each with their own unique IDs across all inventory types. One master inventory table which lists...

>> I think debate between developers about DAO vs ADO is running all the time but with pleasure i want to find out about your point of view. << They're just two different ways to do essentially the same thing. ADO does some things that DAO can't (quite a bit, actually), but DAO is more...

>> this will work but not for create or drop statements. << Again, I'm curious to a specific scenario where this doesn't work. Can you supply one? I believe this to be incorrect, and that you should in fact be able to execute any DDL/DML from a passthrough (provided the connection has the...

Using a passthrough, this shouldn't matter (it still gets passed direct to the target server) I'm not sure that's correct... why do you feel you must use ADODB (as opposed to a DAO passthrough?) What, specifically? Exact error messages and code being executed would be ideal for us to help...

Much of the O365 Excel OM is being ported to JS (AFIAK), but I don't think it'll ever fully replace VBA. JS in general has taken the programming world by storm in the past 5 years or so anyway. Who'da thought. On the plus side, like VBA, it's very easy to learn. On the downside, it's an...

Somewhere I have a template form and accompanying class module that creates a wizard shell, and you load it up and point a bunch of subforms to it, one for each page. The shell is a form with a header and footer buttons (next, previous, finish, cancel as applicable) and is responsible for...

Is there a specific scenario you can replicate and explain here so we can see? I'm with static on this one.

I'm not sure why you wouldn't... as stated, Access forwards the complete, unaltered statement directly to SQL Server, which will execute whatever you throw at it (provided the connection has the correct permissions of course). Also, to run a script file "automatically" (without even having to...

>> But just because you can do something doesn't make it efficient << Great point. AFIAK, any time you have a heterogeneous query between Access (JET/ACE) and another ODBC datasource (SQL Server, MySQL, etc), it tends to become a headache for the driver to resolve and results in a huge...

Generally speaking: 200 codes (200-299) are "OK" 300 codes are redirects to other pages 400 codes are errors on your part (bad URL, bad format) 500 codes are errors on the web server's part Keep in mind that it's entirely up to the web server what status code will be reported. Just because...

I don't think it's entirely farfetched to want to show data in a grid format like that. Access doesn't make it easy to do so, though. The problem with this situation (normalization/best practice issues aside) is that it's not easy to create controls on the fly. In fact, if you plan to...

I highly agree with Mark. Changing code from code should only really be done as part of development or build procedures, and not something for runtime/once deployed. You can easily refactor it the way he suggested, which is a good pattern to follow in general anyway. That said, if you're dead...

>> Microsoft Access can't find the field 'chkCheckBox1' referred to in your expression. << Be explicit: Me.Controls("chkCheckBox" & Trim(Str(i))).Value = True (Colin's code is looking for Fields, as that's the default collection of Me... instead reference the Controls collection explicitly...

You can also turn off AllowAdditions in the form properties. I've always done that rather than using the DataEntry property (no particular reason why, except the the AllowAdditions/Edits/Deletes seemed a more semantic set of properties to me) Cheers

Your runtime 2465 is because you didn't copy Colin's code exactly. The method he's using is using an integer counter to represent the 1-5 portions of your checkbox names, then looping while incrementing the number each time. It's unnecessary (and incorrect) to put all control names within...

This is a bit of a pet peeve of mine - .Value is not the default... a reference to the control object itself is what you point to when you don't use .Value. The Value property is what gets resolved if the runtime determines that you're trying to assign a basic type to something, but it is not...