Viewing 6 posts - 1 through 6 (of 6 total)
Thanks for the quick reply Antares686.
So is this better:
SELECT Person.PersonID, Person.Firstname, Person.Lastname,
Person.Department, Person.middlename, Task.TaskID,
Task.TimeFrom, Task.TimeTo, Task.Task, Task.TaskDate
FROM Person INNER JOIN
...
February 6, 2003 at 6:05 am
OK great.
As for my next table - Person
PersonID - PK
Firstname
Lastname
Department
Would it be advisable to make PersonID an IDENTITY column also?
There will be about 10 people using this database but I...
February 5, 2003 at 4:50 am
Right, thanks Antares.
But, being a beginner, this has raised another question:
This was my original table
tbl_task
taskID (PK)
PersonID (FK)
Task
TimeFrom
TimeTo
Taskdate
So could I redo this table to look like this:
CREATE TABLE [tbl_Task] (
[idx] [int]...
January 31, 2003 at 6:12 am
That's great Scorpion_66, it's much clearer now.
The thing that is confusing me is where the SQL stops and the VB begins. I'm going to read up on VB some...
October 11, 2002 at 8:47 am
Hi
So I'd pre generate the numbers for the different engineers and then use a trigger to insert the ID numbers when 'Bob' filled in a form?
Thanks for the advice, your...
October 11, 2002 at 2:04 am
Hi
Scorpian_66: What you say makes sense and I've changed my model now to the 2 tables, Person -> Task.
I'm trying to think about the end result which will be a...
October 10, 2002 at 9:52 am
Viewing 6 posts - 1 through 6 (of 6 total)