Search results

Yes, I did. I use late binding because I originally had a problem with two different versions of Office on a computer. Access 2010 and the rest Office 2019. So there are no references missing because both have the same four references. Thanks for checking on this point, but it isn't the cause...

I was working on a laptop earlier that had Office 2019 and was getting the error messages. When I went back to my desktop computer with Offfice 2010 the original code works fine. So it isn't my data. Or is it?

I will post my strip down DB as I want to know why this wouldn't work after years of working OK, but i got it to work using the following: DaySort1...

I've thought Will take some doing to extract some data and post the DB, and I do appreciate your help.

my query which is throwing the error messages is essentially the same as yours. SELECT tblSalesAndSchedules.Day1, InStr(1,"SuMoTuWeThFrSa",Left([Day1],2)) AS DaySort FROM tblSalesAndSchedules ORDER BY InStr(1,"SuMoTuWeThFrSa",Left([Day1],2));

Also argument count mismatch

I get #Error on mine.

Sorry fr all the confusion. The field is Day1 not Date1 and while your query will run on my computer using Access 2019, it looks like this: Query1 Query1 Date1 DaySort Sun 1 Sun 1 Mon 3 Mon 3 Tue 5 Tue 5 Wed 7 Wed 7 thu 9 Thu 9 Fri 11 Sat 13

yes there is, but it is not Date1. Probably should just think of it as DayOfWeek. The actual date has no bearing on this query and might not be the actual current day of this month's week. There is a date field but it is the contract start date and it can be several years ago. I hope I am...

I want to sort by weekday. Sun first, Mon second, etc.

Sorry Three not tree. On my wife's laptop and my fingers don't fit it.

Date1 is a tree letter day of week abbreviation, i.e. Mon, Tue, etc.

I have a query where one of the fields is [Date1]. In the query I have the following to sort [Day1] by the day of the week. That is, Sun first, Monday second, etc. DaySort: InStr(1,"SuMoTuWeThFrSa",Left([Day1],2)) Was using Access 2010 now using 2019 and this is giving me an error. Never had...

The batch file update is the best way to handle this. I put a copy of the new front end on the server, link it to the back end on the server and then send everyone who will use this DB and email message to "Update Your Front End". They all have a batch file on their desktop that will update...

some Days I am just brain dead. Sorry for the post. Figured it out. I had inavertantly left in some code that triggered an error message that set off this pop up. Shame on me.

OK, it should have read the last line End if. And the code is not highlighted, the message box just pops up.

I wrote the following code for my Access 2010 program:and it worked like a charm. Dim DayVal As Long DayVal = Weekday(Date, 1) 'Set first Day of Week, in this case Sunday. If (DayVal = 6 And Hour(Now) > 15) Then Call cmdZipAndEmail_Click End And when I transferred it to Access 2019 I get the...

Thanks for the info on the "memo" vs "long text". The others I think I have covered.

Yes, 2010 has memo fields and 2019 has long text. I just wanted to know if the difference was real or imaginary. I am going to go with not changing the old field name until I get a problem. And yes, we backup daily! As for the PtrSafe, that was just an explanation of the only coding I had...

I have recently started upgrading the computers at work to all windows 10 and either Office 365 or whatever they call it (Access 2019) from Access 2010. I have 6 different databases and I upgraded all of them. The only changes that I noticed were the declarations, where the new installations...