This part of the app is tracking the three different area of courses the students take at a University. Three grids have to be on a form. This is the way the user wants is. The purpose of the grids is to add a course number to a grid line item, the course information gets called up, then the user enters the student's grade and such. Now the reason there are 3 grids, is because there are (R)equired Courses, (C)oncentration courses, and (O)ther courses. They want these in seperate grids. One issue I am having to deal with is how to use one course table to populate all three grids. If I use Alias as the source, it will pull in all the course, unless I have a status field, and then do a SELECT statement when the form first opens up. But I don't think this will work, because as new courses are getting added, the grid becomes outdated. I'd have to keep re-SELECTing.

Let me further explain the master table is the Students table. The courses are in the Courses table, obv. and the table that contains the line information I'm calling S_lines. I thought about indexing on a filter, but that would have affected all three grids.I also thought about an updateable view, but haven't had much experience with them. One workaround was to create a total of 7 tables! Keep the Students table, of course, but create 3 seperate line tables, and 3 seperate course tables. This did do the trick, but isn't there a more efficient way? I feel like I put a coathanger in the computer!