Search results

Alright, well the good news is the login form seems entirely functional. Thanks you both. I'll won't mark this solved just yet in case anyone else shows up with some insight.

Okay the SQL code looks fine but it looks like you still have the "Enter Course Name" prompt in your OpenReport command. Replace your DoCmd.OpenReport line with this line: DoCmd.OpenReport "Course Completed by Employees", acViewPreview, , "[Course Name] = '" & strParamValue & "'"...

Certainly Windows authentication is secure and I have that running as well. The issue is this program will be installed on two separate workstations that multiple users will be accessing. They won't be switching out the Windows user, only logging into the program. Plus, some users will have...

You're right, that isn't what I was looking for. Open your form in Design view. Then under the design tab click "Property Sheet": Now in the properties tab, make sure the combo box on top is set to "Form". Click the Data tab and copy/paste the code from the "Record Source" box.

Can you copy/paste the form's SQL Code from the Control Source property box?

Hello all! I'm hoping someone can check my work to see if there are any red flags with how I've handled this. I am working on an Access interface linked to a SQL Server Backend, and just completed a password validation routine. To start, I have a trigger in the SQL Server table that converts...

Never mind! Solved it, made a db-wide module.

@Pat Hartman Sorry to bring this up on a 3-year old thread, but I love this idea and want to implement it but I keep getting the "Constants, fixed-length strings, arrays, user-defined types, and declare statements not allowed as Public members of object modules" error message. According to...

Winner winner chicken dinner! This ended up being the solution, with slight adjustments. I had to change it a bit because the conditional formatting wasn't working. Every single text box was enabled for some reason. To see why I put an unbound text box on the form with record source...

The interface I'm building is for an archives, most users will only ever need to view information. I have a bunch of forms for adding/editing records but they will be available only to privileged users. I'll try to play around with your suggestions tomorrow. Thanks for the help.

The ORDER BY syntax was just what Access autofilled into the SQL after I used the query design feature. I've tried adding hidden controls that run the aggregate function but I keep getting an error that the subquery syntax is invalid, and I don't know why. I've checked the syntax in a plain old...

@Pat Hartman Here's the current SQL record source: SELECT PersonItem.PersonIDFK, PersonItem.ItemIDFK, Persons.FamilyName, Persons.GivenName, Persons.CityOfResidence, [FamilyName] & ", " & [GivenName] & " | " & [Position] & " | " & [CityOfResidence] AS FullName, PersonItem.PageNumbers...

Thank you Pat, I'm experimenting with working a DCount into it now, but I don't know how to put an aggregate function into the current record source. Will this have to be a union query?

@CJ_London this is good information, but I don't think I can get it to work as described because the value that determines the visibility (or transparency) of the button is not a field on the subform, it's a separate query. What I would like to do is create a control that displays a value...

Hello, I have a continuous form in which I'd like to set the visibility for a button "cmdViewImages" individually for each record on the form. The form shows the names of a bunch of items in table "Items". The items may or may not have images associated with them in table "Images". If there...

NEVER MIND! I made a foolish mistake. I closed the form without saving when I renamed the control to 'cboImageID'. So the SQL statement was referencing a control that didn't exist. Fixed that, works fine.

Hello all, In my database I have a table "images" that is ODBC linked to a SQL Server table. I have two forms for this table, frmAddImage and frmEditImage. I have no problem adding data and updating data using the two forms, but I cannot delete records using the forms. I can however, delete...

Thank you, I'll be sure to do so in the future.

Thank you for this, I'll revisit the code and see if I can make it more elegant. That actually clears something up for me. I was misinformed to think public/private meant whether or not that function or sub could be called from another sub on the same form. What you say makes more sense.

Thank you @The_Doc_Man ! That makes a lot sense. Based on your explanation, I don't think CASE statements are really necessary with only a few ELSEIFs here, but after I finish this DB my institution wants me to make another one for another department and I'll almost certainly use CASE statements...