Search results

You are right and wrong. IsDate does change the date for testing purpose. To my surprise, the Format function does as well: Computer set to European date system (DD.MM.YY). I have the textboxes "NewDate" and Me!NewDate2 on a form, short date format. I type in 31.2.23, Enter. The AfterUpdate...

isdate() even changes dates to something really unwanted: e.g. 31.2.2023 to 23.2.31 or something like that. In my opinion, isdate() is of quite limited usefullness.

That is exactly the way I'm doing it. 'A file with that name already exists, do you want to overwrite it?' Y click 'Yes' and see above.

Excuse me, but when I'm asked if I want to overwrite a file and confirm yes, I certainly do not expect the program to do otherwise.

Skype: When I download a file sent to me via Skype, and confirm to overwrite an existing file of the same name in the destination folder, the existing file is not overwritten, but Skype saves the downloaded file as 'Filename (1)'. This is absolutely annoying and leads to mistakes when the new...

MajP and Doc_Man, thanks for staying with me. I tried all of your suggestions, no luck (yes, I know about the /decompile - switch). I then created a new database with two new forms A and B, typed the sub lfp_Click in A and voilá! No error. Now, these two new forms work in the old database too...

Private Sub LFP_Click() On Error GoTo Proc_Err Dim frm As Form Dim FormName As String FormName = "ListPrptys" DoCmd.OpenForm FormName, acDesign, , , , acHidden Set frm = Forms(FormName) Exit Sub Proc_Err: MsgBox "Error " & Err.Number & ": " & Err.Description Call...

Thank you. I was not aware of this. I came to this conclusion as well. Not that it helps to explain why it doesn't work for me, when it's a commonly used method. BTW, I tested the code on another machine with a freshly installed version of Access (same version) - no luck. As well, I tested on a...

I'm sorry, a transcription error on my side. The line actually reads DoCmd.OpenForm strFormName, acDesign, , , , acHidden Anyhow, I tried the code opening the form in normal mode. Still Error 438

Thank you, Ranman. I know that the Forms-Collection only contains open forms. I tried with the form already open or opening by docmd.openform in the code. In both cases Error 438.

No matter how, I cannot get Set frm = Forms(FormName) to work. Though used in uncountable solutions, I'm stonewalled by Error 13, Type mismatch or Error 438, Object doesn't support this property or method. What works: Private Sub Test_Click() ListControlProps Me End Sub Public Sub...

Last update and problem solved Thank all of you for trying to solve this and for the other good advice. And I'm truly sorry to report back only now. The devil is in the detail: In fact, one of the subforms manipulated a value in a textbox of the main form. I have no idea why that should...

OK, perhaps we are getting somewhere here. I now searched every setting option in Access and searched Google to find where to turn off assistants (which I am not aware of to be using), no such luck. Any idea?

I think I do understand both circumstances perfectly, and I'm pretty sure I understand the syntax. What I don't understand is, why A) True is translated to 'Verdadero' and appearing as such in the assembled SQL-String when using MWhat and B) Why VBA, after translating, does not understand...

Update: Me.FilterOn=True is working just fine in some Forms, in others it doesn't, no matter where the line is put (FormOpen event, FormLoad, a command-button procedure). And yes, I did a C&R and decompile / recompile. BTW I checked Spanish forums: The suggestions are Me.FilterOn=True, and I...

Eberhard, you made my day ... well, partially. CBool(MWhat) * 1 does work with False (or True) in the calling procedure! However, Me.FilterOn = CBool(True) * 1 does not work, neither does using Verdadero in any form. VBA does not recognize Verdadero and the suggestion when writing the code is...

MRow is declared as Byte on purpose and has nothing to do with the present problem.

Debug.Print CBOOL( -1 ) returns Verdadero, but when I use Verdadero (or Falso for that matter), VBA does not understand it. Using -1 or CBool(-1) in the calling Procedure also produces the error, even CBool(MWhat) does. I did think of this workaround, but it does not work. By the way, lines like...

I recently face strange errors when taking an App to a computer that runs Access in Spanish (I'm developing on an all English System, W10, Office 2013 32 Bit): A simple statement like Me.FilterOn=True asks to introduce the parameter value for Verdadero (Spanish for True); no matter if I then...

Late but... Thanks to all for trying to help. To Pat, yes, I did both. As well, I created a new, blank database, imported all elements and relinked by hand to the BE. Same problem. I give up now, as the problem is annoying, but not lethal to my app. I'm now facing a new problem which IS lethal...