Sorry to hear your friend didn't make the database relational. I hope she doesn't build them for a living. ;)
Anyway, yes, your tasks would likely have to be stored in a table. That's the easiest option. As for the numbering, it would probably be easiest to have your tasks automatically numbered 1, 2, 3 and later just put the label "JPR " in fromt of every task number when printing out reports or generating queries. You can use the Autonum feature to automatically number each task as new tasks are entered into your database. I suggest getting a good book on Access and relational databases before embarking on this project. As you have already found out, once you're stuck with a bad design there's no going back and "fixing" it. --- In [email protected], ward watson <ward_wat...@...> wrote: > > Question... > > I'm somewhat new to the Access world. I currently have an Access data base > that was built by a friend of mine several years ago. She went above and > beyond the call building it for me, however I find myself in a situation > where I need to update what I need and she is no longer available to do or > make any changes for me. For some time I've wanted to learn how to build my > own data base so when things come up I'm not up a creek. The existing > database was not built as a relational database so it's way to complicated to > change what I need changed. > > I've been working through the Microsoft Access tutorial with some success, > however I still have questions. > > Question #1 - The "tasks" that I need to track must be in a table - Correct? > > Question #2 - So let's say they need to complete what we call JPR's and they > are numbered JPR 1, JPR 2, JPR 3, would I build a table with these in the > fields? > > I'm going to have many more questions before I'm done, so I hope you all > don't mind my many e-mails to come. > > Thanks in advance, > > Ward Watson > Training Officer; Pleasant View Fire Department > > > > > [Non-text portions of this message have been removed] >
