Search results

Usually the term Factory is used for such a class.

Error? What error? The message you mentioned is a friendly reminder/question that your code change will cause the running application to be stopped. It is not an error! This behavior is perfectly normal. Once you start your application by either explicitly running code from one of your Access...

What do you mean with "When I go to debug"?

Unfortunately, there is little documentation on internals of the JET/ACE-Engine and the the SHOWPLAN output. So, my explanations are meant more as educated guesses than absolute facts. Because it makes the subsequent join in 03 easier (less resource intensive) if both sets of records joined are...

"The first time" means if you try to compile the created database file a second time it works? Or do you mean if worked for months and now it fails for the first time? Do you import into a newly created blank Access file or do you import into a file already existing for some time? I think, the...

@Gasman , I suggested *you* create a minimal sample db primarily because in the process it is very likely that *you* will find the cause of the problem. Excuse me? There are several problems with this database. First, there are references missing (Excel, VBA Extensibility) and thus the whole...

I tried to reproduce this issue based on your description in A365 V2507 Build 16.0.19029.20208 32-bit, but I had no luck. Using the expression Val([txtCarbsCalc])>TempVars("CarbLimit") does work as expected for me. If you want to pursue this further, I suggest you create and upload a minimal...

NO. The Access Runtime is a different edition of Access than the full edition. If you install the full edition but do not license it, it will be degraded to "read-only" operation, which has similar limitations as the runtime edition, but is still very different in detail.

Did you actually the read the announcement you linked to? The Salesforce ODBC drives *is* built into Access and will now be removed. That is what the announcement was about.

There was such an issue with Microsoft's own SCC plug-in for Access. And, I agree, this was a major nuisance. AFAIK, all current source code control add-ins do not require to explicitly check out before making changes. For Git based version control, the Check Out step is generally no more part...

I don't think there are any other ODBC drivers built into Microsoft Access. Does this answer your question?

What means "fail to work" exactly? Does it raise an error or does it appear to do nothing? - The latter would be expected when there is a valid date in the selected format as per Windows Regional Settings already. Also, please note: YYYY/MM/DD is not an ISO date format. The ISO date format...

Well, you created an indirect validation rule with your VBA code in combination with the Short Date format of the controls... Here you force YYYY/MM/DD as date format, which might not be a valid date format on the target (runtime) computer. - And, actually, I don't think YYYY/MM/DD is a valid...

Is there a Validation Rule defined for the control in the form? Does this Validation Rule expect the date to be in a specific format?

Please show the code that fails. The most common cause of such problems is when dates are passed on as text and not in Date/Time typed variables.

That was one of the reasons I asked for a simple reproducible example of the problem. If you just report an obscure problem with an error occurring for some of thousands of files and only include a vague description of your code, the chances of Microsoft fixing this are indeed zero. However, if...

Well, that's the point of defining column headers, isn't it? But, as a reminder, particularly for newbies, that might be sensible.

Can you provide a minimal sample db to reproduce the issue? PS: You also should have mentioned that you asked about the same problem before.

I believe this will only work if the query is the Record source of the form in question. In this case you can also omit "Form.". PS: Of course, if there are ambiguities between form controls and table columns in the query, you should not omit "Form."

I do not expect this to work. Even though, the error should be something along the lines of "The specified Recordsource is invalid or does not exist"