Search results

It doesn't. That is indeed a problem in such a scenario. However, if it is about security/permissions, I would integrate restricting the records in the underlying query, preferably on a database server.

And what do you feel is the problem with that?

You are not using the proper delimiters for a date: #

The order in the list of references in the dialog also depicts the priority of the references. Moving a library, which might be potentially missing, to the lower end of the list will reduce, but not eliminate, the risk of this causing problems with functions from other libraries.

Which zip? You must download the XstReader.zip from the releases section, not a zip of the source code.

Strictly speaking the documentation is correct and precise. If you actually deal with an container control, its child controls will be on the container control, not in it. - Microsoft is using this terminology consistently. I agree that the wording in the documentation has some potential to...

An universal problem with text delimiters inside the delimited text. So, rather beware to pass on raw user text input with adequate preprocessing.

No doubt, they did. If they would do the same for Excel and Word, you can expect this to be multiplied by 1000. And keep in mind: The transition to "New Outlook" is nowhere near completion. Most organizations depending on Outlook automation won't have switched to New Outlook yet.

I'm not aware of any plan for this. I'm sure they would like to do that. However, VBA usage in Word and Excel is probably a thousand times more common than in Outlook. So, for now they cannot do anything like this without antagonizing a huge number of their customers.

It's actually not. Best use the ISO date format because it is universally unambiguous for computers and for developers.

No. If that were the reason, they could have just disabled or removed VBA/Automation in/of Outlook. The primary reason is that there are three different editions of Outlook (desktop/web/mobile) with completely different code bases. For calendar and tasks there are even more. This creates huge...

Yes. No, of course not. How should users have different permissions if their permissions are defined by a single AD Group. You need to create one AD Group for every set of permissions.

Were the ODBC tables relinked on PC2 for one of the applications but not the other? Did you check the data type of REGISTRATION_DATE in the table in Access? Are they the same in both applications? Does it make a difference if you explicitly relink the tables on PC2?

While I also think single quotes are better for SQL, this was not the problem you were dealing with. Look at the criterion value from your original post: It's hard to see, so lets format this with a non-proportional font: "Microsoft*'" -> There is an single quote at the end, which is part of...

It was Sybase SQL Anywhere for ~20 years before SAP bought them. Review all options in the ODBC driver configuration dialog whether there is something related to BigInt. There was a "Keys in SQL Statistics" option required for Access according to some documentation. - However, it doesn't seem...

Relink the Sybase tables. Configuration changes affecting ODBC linked tables usually only become active after the tables are relinked with the new configuration.

This should still be correct. Can you provide a reproducible example were it fails? Just send a WM_CLOSE message to the form window.

Why did you split this into two steps? You could also include the DogId in the Insert statement. If Reccount = 0 Then CurrentDb.Execute ("INSERT INTO tblDNAProfile (dnatestid, dnacategoryid, dnatypeid, DogId ) " & _ "SELECT dnatestid, dnacategoryid...

All your references to ResultPromote have a trailing space inside the square brackets. The square brackets make this space part of the Name that is being searched for. This control cannot be found and thus the error is raised. I believe, you cannot (and more importantly, absolutely should not!)...

None of the DAO.FieldX classes has an AttachmentCount property. - That's what the error message is trying to tell you. Isn't it enough to just check for: Not .....Fields("Sigend_Form").Value Is Nothing ?