Recent content by ScottGem

Jass, This is a 9 year old thread. If something didn't work for you. Please ask a new question detailing what you tried and why it didn't work.

fsagwe, I'm not entirely clear on your question. Also you should start a new question rather than piggyback on a 9 yr old thread. You come up with a join table to create two 1:many relationships to both sides of a many to many as explained in the thread. In its simplest a join table consist of...

Not sure what you mean, but you can use a query instead of a table within a SQL statement. So the SQL shown in this thread should work if you just substitute querynames. Hope this helps, Scott<> ScottGem's Blog Microsoft Access MVP 2007 Author: Microsoft Office Access 2007 VBA

Thanks Darbid, That was enough to get me to the right place and successfully do what I wanted. Appreciate the help. Scott<>

I've been searching for this and haven't found it. I have the code to create either a Task or appointment from within an Access module. Works great. But I want to be able to update the item if changes are made within Access. For example: if a task is marked complete in the Access database, I...

First its not a good idea to piggyback your question on someone elses. This can lead to confusion. You should start a new thread. You really shouldn't have two tables. You should have a field that indicates whether a person is a prospect or a customer. Then all you would need to do is change...

The type of problem is a good idea, from there you can limit your link to one field. with the type field defining what you are linking to.

Several things. 1) You don't need a CallPlacedDay field. That can be extracted from the CallDate. That also means you can eliminate your Days table. 2) It looks like you have several lookup tables. These should be named with a tlu prefix to designate them. Its also not recommended to create...

No attachment!

Doesn't change what I said. Since its possible that the computer is not the one normally assigned to the user reporting the problem, then you need capture the info. Later on, once the problem is accurately diagnosed you can remove the computer FK if you want.

If a person can report problems relating to different computers (i.e. a person is not assigned to a specific computer, then you have to use foreign keys to both the person and computer tables.

First we don't store calculated values. Second, I don't understand your database, you only have a Time In not a Time Out. I also couldn't find your Calc code. Calculating elapsed time is easy: DateDiff("n",TimeIn,timeOut) will give you the time in minutes. You then divide by 60 to get hours...

Why not just use the combo wizard to create a search combo in your form header?

duplicate please delete

As I said earlier we do not store calculated values. There is no need to store this data.