Search results

Hi, RichM, I'm working on the form I now have well visualized, but I'm also wondering if I can start the process from a form I've already got by putting in a command button called "hire" The form I have is for tracking the application. On the top of the form there's the posting information...

RichM, Thanks for the thoughts. Your "script" is pretty accurate. Let me elaborate: 1) Make a Position (if not already existing) 2) Make a Posting and connect to an existing Position 3) Make Applicants (if not already existing) 4) Connect Applicants to existing Postings, repeat as needed...

Doc, Thanks for your response. I am not having trouble keeping track of my data sources, and was not confused until I was asked questions that made me doubt what I had done. The database I have created matches the flow of paper that runs through the Human resources office I am designing it...

All right, well that's okay... I've learned something. I'd also like to learn how to create a command button to hire a person... Any thoughts there? ;)

Wouldn't it handle a many to many? One posting to many applications, one application to many postings... Is this what I had before I changed it all up? Ah, me...

tblJunction All right, so I'm re-working all this stuff and I've hit a snag... I've changed all my stuff around and here's what I'm thinking: I need to put tblJunction back because one application can apply to multiple postings (provided it meets certain criteria...) There's currently a...

Hi, RichM! I'm glad you had a nice time in CT... I can't believe it's snowing out there. We're supposed to get flurries this week sometime, but nothing we can really call "snow." I love New England in the Autumn. Crisp air, and beautiful colors. Tea and sweaters. Cozy. (Have to admit...

The date I'm entering isn't really "criteria..." It's a variable. The query does a kind of datediff thing between a date and this date, and then the criteria is the result (difference in month) = 12. (I get the same set of problems with an identical query except the criteria is = 6. So it...

I tried entering #11/1/02# and it said "The Value you entered isn't valid for this field." I tried leaving it blank, then tried cutting and pasting in both the report and the query: here's what happened: Report: in both, it gave the same message "This expression is typed incorrectly..."...

In the tables, the dates are all defined as dates. Is there any way the calculated dates aren't formatted correctly? In the parameter part of the SQL I've put DateTime as the data type for what the user is supposed to enter. It won't accept things not in short date format... And all the...

Yeah, we're running both on the same machine. It does the same on every machine we've tried it on so far (5 of them...) Such a strange problem...

Hi, Col!! Yeah, the date is supposed to be in the future. It's for determining whose supervisors need to fill out evaluations in a given month. (annual and semi-annual) So they run the report in advance so they can send out the evaluations to the supervisors and (hopefully) get them back in a...

thanks for teh reply We've tried that, though... we've also tried 11-01-02 and November 11, 2002 and 11/1/2002 (and all of their variants.)

Hey everyone, I've searched the forums, and found some stuff on this topic, but somehow it doesn't seem to quite answer my question. I'm creating a db in two parts. The users have part One already and use it. It's been going pretty well, but then this problem occured. I made a copy of the...

ooohh! you want to move those fields to tblJunction! I thought you wanted to just put them all in one table. Yeah, I may be able to do that... I'll look at it. Thanks for your help there. But I'm still not sure how to go about what I wanted to do originally... I don't know who Ian Sholes...

I would have to re-enter the applicant's information every time they applied for another position. (name, ssn, address) I would not want to edit the application tracking info every time someone applied for a job, so that I could have a history of their applications.

Ooh! just realized something! ApplicationID (in tblJunction) is different every time a person has an application. So one SSN can have many ApplicationIDs... therefore, the person will not be in the tblJunction more than once.

Okay, let's see: If I want to track the positions a person has applied for, and don't want to enter the whole name and ssn every time a person applies for a job, isn't it better to have a table with that information? I currently have a form that shows a posting, with a sub-form listing...

RichM, Some (more) clarifications: First, you said: <<I'm still not clear why there is a table for both Applicants and Applications. This seems like one conceptual entity to me. If the person who is an Applicant wants to apply for 2 or more Postings then the person's unique ID (whatever it is)...

RichM, Sorry for the confusion. The information for all applicants needs to be the same, whether they are employees or not. tblEmployees simply holds a list of all the employees and their positions. It was the original part of the database, before the postings and applications and all that...