No problem. I have found a way around it, but it is very, very slow. I use it when cross-referancing two tables, by using an ID from one table (student info) to make a SQL Select Where for another table (print options for the name tag, etc, based on the ID).
If I use SQL Select Where, and refer to a unique key, I get one record. How do I transfer one column from that query to a variable in VB? For now, I've found a way around it, but I know there has to be a better way (I just haven't found it!).
If I use SQL Insert, Select Where, I can add only the record I want into an empty table. If I refer to that table on a report (or form), I can take the data off the report and put it into a variable.
Enter your message below
Sign in or Join us (it's free).