Andre Bazin,

May I ask why each student needs to have an entire table on their own?

No, it's possible.

Sincerely,

Chris O.

It may or may not be impossible: but it's an extremely ill-advised thing
to do. There is simply no good reason _ever_ to do what is, essentially,
code data into table names.

The thing to do is to have one big DSSR table with _field_ called
StudentName that is pointed at the FirstName (or whatever) in the Student
table. Then, to look at John's DSSRs, you simply use a query with a
criterion like "WHERE StudentName = ""John""".

Much easier, no?

All the best

Tim F

It's a difficult task because it is AN EXTREMELY BAD IDEA.

Storing data in tablenames is *NEVER* either necessary nor
appropriate.

If you want to see all of John's data, use a Query selecting just his
data from tbl_DSSR. This Query can be used as the recordsource for a
Form or Report, can be exported to an external file, can be edited,
etc. etc. If you're concerned about security, the Query can be set up
so that John can edit only his own data as well.

If you have some specific reason why you feel that you must violate
relational design principles in this way, please explain. It's
*possible* to do what you ask with some VBA code, but I cannot imagine
a good reason for doing so.

                 John W. Vinson[MVP]