Search results

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

I fully agree with this. First, we must consider that we are talking about the Unload event here. Access is telling us: "I'm will unload this form immediately. If you want to run some code before that, do it now!" The code we might put into the Unload event procedure is not really part of the...

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.

JFTR: In A2002 the form will also close when there is an End statement in the Unload event. What? I'm afraid, you lost me there. Which code was allowed to run? Why wasn't End applied correctly if the form closes? - Any documentation link to support this opinion? Why is End supposed to close...

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 ?

Technically you can do that. But, as others in this thread, I strongly advise against doing so. You change the variables from being exclusive to the procedure they are declared in to global or module level variables, which can be accessed from a wide variety of procedures. Then previously...

Yes, that should work. It is generally advisable to copy the front-end to each user's local hard disk and thus give them their own file for exclusive use.

DoCmd.RunSQL "UPDATE tbl_Net_TicketDays SET " & [Forms]![frmBackground]![subfrmTickets]![txtTableFieldDay] & " = [txtMonday]" (Requires txtMonday to be in the active form, otherwise you will need to fully qualify it with Forms!...) Please note: This will update all records in the table! You...

I like this much better and I'm not aware of any naming conflicts, which of course doesn't mean much.