Ok... I played with it a little more and I figured out the problem. The format of the combobox was not set up correctly. The column widths were set to 0";1";1". So, the password was showing in the combobox, but the PWReset field wasn't there at all, so the code couldn't find it. When I added...
I am trying to create a database that has a login form for users. I found some code that seems like it should work, but it's not working completely. The code is shown below. Everything seems to work except opening the password change form. The only things on the login form are a combobox...
Good Morning!
Let me first explain how this database is set up before I get into what exactly I need help with. The company I work for has a report that is sent out weekly to the executives. Each department has a section in this report. Before this week, each department typed something in...
Ok I got it... stupid me had a slash in the name of the file, which isn't valid. So, that is what was causing the problem. It works well. Thank you again.
ok... I tried that. Here is how I put it into the code:
Sub test()
Dim ws As Worksheet, wsSummary As Worksheet, lRow As Long, bCOPY As Boolean
Set wsSummary = Sheets("Final")
Application.ScreenUpdating = False
For Each ws In Worksheets
With ws...
I have the following code:
Sub test()
Dim ws As Worksheet, wsSummary As Worksheet, lRow As Long, bCOPY As Boolean
Set wsSummary = Sheets("Final")
Application.ScreenUpdating = False
For Each ws In Worksheets
With ws
Select Case .Name...
Each line in the PO file will only be associated with one Job. I don't think you're understanding the problem. If I add another field to the PO table in Access, JobID, how will I be able to keep the PO table updated? The Excel file will not have the JobID field at all.
I would say the PO# itself is a unique identifier, but some PO's have more than one line and when it exports, the PO# will appear for each line. So I guess the answer to your question is no. And, if there is a way to create one, I don't know how. I could look into it.
And there lies the problem...
The Excel file (the export from the purchasing software) essentially IS the PO table in Access. However, if I'm going to relate the table to the Jobs, I will need to enter the JobID field to relate the two. The JobID is not going to be in the Excel file. The POs...
MazeWorx - sounds like that would work... problem is, I don't really know how to do those things... so I'll have to play around with it and figure all that out.
Andrzejek - I think you misunderstood what I said. The VesselID is in the table already. I am saying I would need to add the JobID...
I have a Vessel Table, where the Vessel ID is the primary key. Then, the Vessel ID is a foreign key in both the jobs table and the PO table. One boat may have multiple jobs. I have a Job ID field that's the primary key in the jobs table. I assume I'd have to add that into the PO table as a...
How? There are thousands and thousands of purchase orders. And, it would need to be updated at least twice a week. Is there a way to have access look at an excel spreadsheet and update the table with the changes?
I have two tables. One is for jobs that require a boat to be down for repairs. The other is a list of Purchase Orders. I would like to be able to somehow select which purchase orders are associated with the job. The problem is, the purchase order list gets overwritten twice a week because it...
Cool. That works too! For the purposes of what I'm going to be doing with it, the VBA solution works the best. However, it's nice to learn a new formula! Thanks!
Ok, this may seem like a stupid question, but I know little to nothing about VBA. I right clicked on Sheet1 and clicked View Code and pasted the code there. Is this correct? If so, how do I run it?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.