Search results

as some more basic instructions: click on the first table and go to the create ribbon. click on the button that says "form" (not "form design", just "form) - it should be about the 5th button from the left on that ribbon. save the form with a sensible name. i recommend "frmEmployees" the "frm"...

ok, step by step is pretty much my first post. can you explain what you've tried so far? and can you explain what didn't work, what did you expect and what did you actually get? i'll have a look at your DB later - for now, it's dinner time, then it will be bed time.

what have you tried already, and what is it giving you different to how you'd like it?

hi westbandits, welcome to the forums. first off, to create a form you can use the form wizard. make your main form based off the employee data, including the EmployeeID. then make a separate form one each for the data in tables B, C, D, E - make sure to include the EmployeeID in each of these...

sorry to bring up an old post, but i need to add some technical detail to the code i posted. i just tried using this code in another database at work that i'm splitting (copy paste this and a module straight from one to the other with minor adjustment (i.e., the form to open when finished)) and...

access does not, and should ever not, on principle of referential integrity, reassign previously used numbers. this is why Khalid was concerned in his first post, because HIS access WAS re-assigning previously used numbers. imagine this scenario - you have an employee database with employeeIDs...

Khalid said in his next post he actually tried that as instructed, but after compact-and-repair, Access 2010 still re-set the ID numbering... ..weird.

have you tried looking for hot-fixes or searching the MS site?

i couldn't agree more.

took me a while to get my head around it too. aside from this forum, you can find many examples and advices on the web. in a google search, i entered "access junction tables" and got very many useful hits. here is a selection: http://www.foresightsoftware.com/AccessJunctionTables.htm...

"the way it is" is that computer programs work in a logical, systematic way. just tell your boss it cannot be done 'his way' without making a mess of things. eventually he'll come around to the new system (he might not like change, but i'm sure your boss has had to accept and deal with changes...

this just shows my age, but: how did people script VBA before VBE? there must have been a window of some sort available to input the code?

i've always understood "VBE" to mean "Visual Basic Editor"....?

glad you got it to work :) and thanks for the feedback, too.

not happening in my VBE... have you checked preference, hotfixes, service packs? etc

you're better off to make a subform for your customer status - then you can view their entire history while looking at just them - makes for easy judgement on them - e.g., repeat offenders? to do this, you need to make a form "sfrmCustomerStatus" ("sfrm" means it will be sub form), make it...

why don't you have the employees down the page instead? and the work details along the top - that way, if you change your employees the report automatically draws on all the employees you have. and i'm afraid your table "Employee Worksheet" is not normalised. what i think you need is probably a...

why don't you look at the calendar form your mate made for you and reverse engineer?

TIP: if your users want to add a value that does not exist, you can use the "Not in list" event to manage additions...

sorry, i didn't mean that you change this in your database, just that i wanted to know what these were so that i could make a better judgement on how to arrange your tables. glad you figured it out, though.