Search results

The error hasn't popped up in the last few days. Not to say that it's fixed or anything. Just not sure whether to leave this open or not.

Ah gotcha.

Yes, the tables are stored on a password protected BE stored on a shared server. A max of 4 users (including myself) downloads a fresh copy of the FE onto their hard drive, by means of a batch file, every time they open the db. As far as I know, no one other than me creates queries.

No GUsername problems so far. Ooh. I've seen that option during the File > Save As bit. Does an .accde stop users from creating/editing objects: forms, tables, queries, reports, macros, modules, etc?

Okay. Went back to all of my forms to include Option Compare Database and Option Explicit. Ran the Compile and nothing came up, which is suspicious. I'll deploy these changes and see if this error comes back on Monday.

Oh darn. I went back to my login form code and changed it to: strSQL = "SELECT UserName, Password FROM tbl_login WHERE UserName = """ & Me.txt_username.Value & """ AND Password = """ & Me.txt_password.Value & """" Set db = CurrentDb Set rst = db.OpenRecordset(strSQL) If rst.EOF Then...

I'm confused. I thought GUserName = rst.Fields("UserName").Value did the job. If it's not, how do I change it (or add) so it does?

With my luck, it's probably a mix of all 3.

So in my database, I have 4 forms that have a Editor and Edit Date fields: Work Order, Purchase Order, Customer, and Inventory. They all have a Before Update event. I've noticed that some of them have Me.<date field>.Value = Date where others don't have the .Value bit. Secondly, I went back to...

So yesterday the error popped up for one of my users and highlighted the line Me.EditedBy.Value = GUserName like in post #1. I hovered over Me.EditedBy.Value and it said Me.Edited.Value = "<user's username>". When I hovered over GUserName it said GUserName = "" I'm so new at VBA, so I'm not...

@CJ_London Thank you for explaining and with an example. It's easier to learn with examples/visuals. I'll go ahead and implement those recommendations. So the bit where I have Option Compare Database 'Username used for updating several forms Public GUserName As String is saved as a module...

Hmm. I'm not sure I understand. *sigh* Perhaps that's something I can try if this problem persists, but I've been playing with my test records for the past day and it hasn't come up. Plus, that last part about might overcoming error but doesn't exactly help and can allow bad data isn't...

@CJ_London This login sub is code I found online. I'm not sure where to have it exit. Come to think of it, I don't have any error handling. *facepalm* The error hasn't appeared yet, so I'll keep this in mind! Ah, gotcha. What is the reason for putting Option Explicit for all modules? FYI, I...

Yes, I do have a user table with username and password. Could you explain that bit about login initials? I checked my user table and both username and password allow ZLS. 1) Is that like default settings when you create a Short Text field? And 2) Would it make a difference if I went back to my...

@CJ_London I'm not sure if this helps, but in my login for code: GUserName = rst.Fields("UserName").Value

Well, I know the data type is string based on the public module. But how would I find the value or assign a value? I had no idea about the failed login. But in any case, they can't access the Main Menu with a failed login. The only options they have is to enter a current username/password or...

For a long time, we've had no issue with this, but we've been getting this error a few times now, and I'm not sure what's going on. Just in case, I checked my table: Here's the segments of code I use for this: Option Compare Database 'Username used for updating several forms Public...

Tried the same thing with my Purchase Orders form and that didn't work either. I suppose I can cut my losses and just have it output to a folder on the shared server with the field as the name of the file. The primary problem was addressed, so thank you @The_Doc_Man !

I knew that using # as a shortcut for 'number' would come back to haunt me. Even when I changed that line to the following (brackets around WorkOrder#), I still got that error: DoCmd.OutputTo acOutputReport, "WorkOrderRpt" & CStr(Me.[WorkOrder#]), "PDFFormat(*.pdf)", "", False, "", ...

I tried this on another form, but I get this error: ' Saves current Work Order as a PDF ' Improved version of the PDf macro button Private Sub cmdWO_PDF_Click() 'Added 1/8/2021 DoCmd.OpenReport "WorkOrderRpt", acViewReport, "", "[WorkOrders].[WorkOrder#]= " & Me.[WorkOrder#], acNormal...