Questions

How to make a form in Access using a button?

+
0 Votes
Locked

How to make a form in Access using a button?

Darryl~ Moderator
Here's an explanation of what I'm trying to do (I'm not even sure if it's possible).

I'm making a little database in MS Access 2007 for one of our remote locations that will allow them to run a few reports listing hours employees have missed and the reasons (that was the easy part) along with some forms that will allow them to key in hours worked for each employee (they only have about 30 employees).

So when setting up the first part I created a few lookup tables, one being an "Employees" table.....I have created a form that I can select employees from a dropdown list (combo box) that automatically opens a form for that employee based on a table that was automatically created when the employee was "created".....this is where I'm having my problem.

When creating the employee, I have a button that runs a "make table" query & names the table as the employee's name, this is the table the above form must be based on. Is there a way that anyone is aware of to automatically make a "split form" using a button.....I know it seems like a silly request as all you have to do is highlight the desired table in the list of tables, click the "Create" tab & click "Split Form" in the forms section then just give it a name but you have to realize the skill level of the end users isn't all that high. This remote location has a fairly high employee turnover rate and I really don't want to be driving out to it every time they have a new employee.

Anybody have any ideas?
  • +
    1 Votes
    john.a.wills

    It seems to me that you may be doing things in too complicated a way. I would be inclined to have a single table of employees, creating a new row for a new employee. Can you show us the table description so that we have some idea of why you are doing things with 30 tables rather than with one table of 30 rows?

    +
    0 Votes
    Darryl~ Moderator

    That was my original thought also (a single table) but then they complained about all the extra work by continously typing in the date (they key the hours in weekly, not daily)...myself, I would be happy with the little date picker beside the box so I could either select it or key it in.....but oh no.....so that's basically why I have the 31 tables....the date fields are already filled......I know, it's a very clunky way of doing things....I don't like it either.

    +
    0 Votes
    john.a.wills

    what you are doing. That may be my fault. Can you perhaps show us your table description(s)?

  • +
    1 Votes
    john.a.wills

    It seems to me that you may be doing things in too complicated a way. I would be inclined to have a single table of employees, creating a new row for a new employee. Can you show us the table description so that we have some idea of why you are doing things with 30 tables rather than with one table of 30 rows?

    +
    0 Votes
    Darryl~ Moderator

    That was my original thought also (a single table) but then they complained about all the extra work by continously typing in the date (they key the hours in weekly, not daily)...myself, I would be happy with the little date picker beside the box so I could either select it or key it in.....but oh no.....so that's basically why I have the 31 tables....the date fields are already filled......I know, it's a very clunky way of doing things....I don't like it either.

    +
    0 Votes
    john.a.wills

    what you are doing. That may be my fault. Can you perhaps show us your table description(s)?