How to handle null in SQL statement

[ultimateguy]

That is correct. The point is to build groups of random questions and then allow the user to make any further customizations that are required.

[Ruegen]

That is correct. The point is to build groups of random questions and then allow the user to make any further customizations that are required.

what stops the same questions from appearing again? (you don't have to answer, just curious)

Since you're simply filtering the table you're not adding or selecting rows.

The user doesn't know which row is being picked by the filter and so they won't know what row to filter out? i.e. row id 157, the particular row in the filtered report you want removed.

I'm assuming there is only one table full of questions and not multiple...?

[ultimateguy]

Nothing would stop the same question from appearing again - the user could just repeat the process. If there are no other questions left that fulfill the criteria then they would have to enter a new one.

I have a single table filled with questions.

You're right, the user doesn't know the ID of the questions being displayed in the report.

So is there a way to do this from within the report?

[Ruegen]

Nothing would stop the same question from appearing again - the user could just repeat the process. If there are no other questions left that fulfill the criteria then they would have to enter a new one.

I have a single table filled with questions.

You're right, the user doesn't know the ID of the questions being displayed in the report.

So is there a way to do this from within the report?

hmm, you could put a text box in the header of a report in report view but not have it or the ID of each row show in print view.

That way they could scroll down the report, pick some ID's of rows they don't want, put the ID in the text box and it could filter out that ONE row (you'd need vba to do more than one or several text boxes)

Then when they print there is no visible IDs and the question they didn't want have gone too.

You could add a checkbox field that lets you select rows you don't want by saying any row checkboxes doesn't show in the report but then you'd need to make a continuous form first.

it's all very messy and I would be doing things in vba to make it work (like examining the row, finding what it had it in before adding a row with similar group information)

maybe june7 has some suggestions before you go further.

[ultimateguy]

I think what I may do is create an empty table and then with VBA, fill that table with the records produced by my SQL statement. Then the user could use a form bound to that table to customize it and make any changes necessary to the questions. When the user is satisfied they then click a button which would generate a report with that table as the record source.

I don't know if this is the most efficient way but it should work.

[Ruegen]

I think what I may do is create an empty table and then with VBA, fill that table with the records produced by my SQL statement. Then the user could use a form bound to that table to customize it and make any changes necessary to the questions. When the user is satisfied they then click a button which would generate a report with that table as the record source.

I don't know if this is the most efficient way but it should work.

I was going to suggest that.

Populate a table with questions using vba (copies) then delete/hide the rows you don't want.

[Ruegen]

Also have an "add row" text box field (you type question in the field, press a button and it adds a row directly into that table, however not in the original questions table - but vba can get around that)