Search results

My quick guess before I go to bed is that you need to use late binding. Check out my long ordeal with this: https://www.access-programmers.co.uk/forums/showthread.php?t=307416&page=5 post # 73.

As I figured, something so simple I was missing it. But just curious, is there away of passing the variable from the one form to the report OnOpen event.

I would like to set the sorting on a report with vba. I know that I can do this via the OnOpen event with code something like: Dim sOrder As String sOrder = "[DateOfContact] Asc" Me.OrderBy = sOrder Me.OrderByOn = True But want I want do to is set the sOrder from a button on another...

Yes it does! Changes to default are made only in design view

Yes it does!

Turkey eaten, family left and I now, after the prodding above that I was not exactly coding it correctly came up with the following. Dim sQuote As String sQuote = """" & Me.txtquote & """" DoCmd.OpenForm "frmMainMenu", acDesign, , , acFormPropertySettings, acHidden...

Regarding having to set the "permanent" default value of an unbound text box, I refer to the following: https://social.msdn.microsoft.com/Forums/office/en-US/3df47f77-2ff5-47e3-8992-0ef0e840dc8c/default-value-of-unbound-text-box?forum=accessdev...

I have a billing database where I want to change a quote or greeting that is displayed on an invoice which I can change at will. I tried all different kinds of options but finally figured out something that would work. But I am not sure if I am doing it correctly. The Main menu has an...

I have updated the code per your suggestions and tested it. It seems to work OK. Was actually very simple to convert the SQL statements. I won't know until Monday afternoon when the user runs her monthly reports it it indeed does work OK. Your help is much appreciated.

I am going to try that today. Definitely would save a lot of work for me.

I have been bugged by the MS update Office 2010: Description of the security update for Office 2010: November 12, 2019 (KB4484127) as posted on https://support.office.com/en-us/article/access-error-query-is-corrupt-fad205a5-9fd4-49f1-be83-f21636caedec. I am able to change some of the...

Guess I will try it on a sample of my db and see what happens. Noting ventured, nothing gained.

I have also been having corruption problems with Access 2010 recently. Since it is a small company with a relatively small DB, less than 100 MB, I thought about using SQL Server 2019 Express for the backend. Is this a relatively simple process and will all my forms, queries, modules, etc...

If you remember on my ever expanding thread: https://www.access-programmers.co.uk/forums/showthread.php?t=307416 On post # 25 I started using the Cstr() function. Others chimed in on this and on post #37 I said I found it on https://access-programmers.co.uk/forums/showthread.php?t=290214...

Yes, same error message.

Gasman: I had the same problem as you in that it failed on the line: .To = Me.EmailToBut will work if you use: .To = Cstr(Me.EmailTo) I think it has something to do with the references, but now I am way over my head.

OK, finally after a long weekend waiting to hear if my newest version worked on the miscreant machine, I then had to wait until our local power company PG&E turned on the power again. Many areas of Northern California are experiencing forced blackouts. The code was tested this afternoon and...

For anyone that might me interested, I changed al the codes that were throwing error messages on my DB and tested it on my home computer, Windows 10 but Office 2010. I only have the four references checked as on DBGuy's email demo. The only thing different that I notices is that I did not have...

Thank you all. I just had to take a few hours off today as my head has been spinning about this subject. The good news is that I think (a big hope here) that part of the problem is the references. I tested the EMail demo from DBGuy and made the same adjustments in references to my email...

I will try your demo again. The demo is about the same as my test DB, but then what do I know. I hope it will work and if so will tell me that my DB is way too complex and is the root of all my problems. Or not. Seems that this problem is rooted in the change from Office 2010 to Office 16 or...