Automatic table

[Don]

Hello,

Can access be programmed to automatically fill a table. Information would be
from the database but selected information would be used ?

 

[Lynn Trapp]

Maybe! Could you be a bit more descriptive about what you are tyring to do?

 

[Brendan Reynolds]

Depends what you mean by 'automatic'. Something has to happen to cause the
code to run. That something could be anything from the clicking of a button,
to the firing of the Timer event of an open form. If you use the Timer
event, then someone has to start Access, open the application, and open the
form, but from then on it will be automatic as long as that form is left
open.

Generally speaking, though, it is often better to use a query to select the
subset of columns and/or rows that you require rather than copying data from
one table to another.

--
Brendan Reynolds (MVP)
http://brenreyn.blogspot.com

The spammers and script-kiddies have succeeded in making it impossible for
me to use a real e-mail address in public newsgroups. E-mail replies to
this post will be deleted without being read. Any e-mail claiming to be
from brenreyn at indigo dot ie that is not digitally signed by me with a
GlobalSign digital certificate is a forgery and should be deleted without
being read. Follow-up questions should in general be posted to the
newsgroup, but if you have a good reason to send me e-mail, you'll find
a useable e-mail address at the URL above.

 

[Don]

Thanks for the response

well, what i am trying to do is, i want an allocation table to fill
automatically by using information from the order table and employee table. i
want the allocation table to check the deadline of order and requirements,
then match these with the employee availability and expertise and put the
order ID, Employee ID in the allocation table.

does this make sense ?

 

[Lynn Trapp]

You probably don't need to have the table filled automatically then. You can
probably create a query that could simply pull the appropriate information
from the order table and the employee table, depending on what your table
structures are like.

 

[Don]

Thank you,

I am still a little confused but i will go back to the drawing board. I
understand what you are trying to say but i cant see how i would implement
this.

Thanks again Lynn

 

[Lynn Trapp]

well, if you will post your table structures here and a sample of what you
would like the data to look like, perhaps someone can help you figure it
out.

 

[John Vinson]

Thank you,

I am still a little confused but i will go back to the drawing board. I
understand what you are trying to say but i cant see how i would implement
this.

Just to clarify - many people new to Access make the assumption
(perhaps colored by experience with spreadsheets or dBase or other
programs) that you must have data in a Table in order to report it or
do anything else with it. This assumption IS WRONG. It is perfectly
normal to store data in several tables, and then create a Query
linking the tables and pulling one field from this table, one field
from that; and basing a Report (or a form, or an export, or even
another query) on this Query. Saving the data redundantly in a new
table is just a timeconsuming extra step.

John W. Vinson[MVP]