Search results

The table are related by a number not by a name. I've added a query to the example called qryShowJoinedTables that shows how typically you use records from two tables.

Take a look at the example in the other thread here. Look at the form and inparticularly the combo for choosing the therapist. It shows as the full name even though the therapist is stored as first name and surname. So the user just chooses the name they want from the combo. The combo is based...

See the example I posted

I attach an example. Note that the combo in the form has two columns, one is not visible (the therapistID) and the other is the full name of the therapist.

You could have appointments for therapists that don't exist for example. Because Access is encouraging you to define lookups at tabular level and in order to do that it must know the relationship to the lookup table. But avoid using them. Read here.

Don't use lookup wizards (if I understand correctly what you mean) Your therapists table should have a unique key. You could have the key made up of two fields i.e. firstname and surname. But there is always the risk here of people changing their name or two people having the same same. It's a...

I am very surprised if a little shocked by you comment. I agree that "relationships" aren't mandatory but by the same token, neither is normalisation. The lines in the relationship view define constraints on the tables. If you've done your design properly and understand your primary/foreign key...

Looping like this is just plain slow. For one thing on every pass of the loop, all the statements in the loop have to be processed (except the on inside the IF statement). If you are not convinced, then run the loop without the query and you will see it is still slow. Just run a bulk query...

Create a single sub report to generate a block. Add it to you main report group so that the sub report runs for each date. At this stage the blocks will be listed vertically so go into Page Setup=>Columns and change the columns to 3. Change the Column layout to "Across then down".

That's good to hear.

So have you changed the incorrect (curly) quotes to the straight ones?

your quotes look different. The quotes on the left look fine. The quotes on the right don't. Take a close look, they are different. What's the error message anyway?

I suggest you install Visual Studio Community from here: https://www.visualstudio.com/vs/visual-studio-express/ This is the latest free edition. Select Visual Basic and you should be good to go. Once installed you can install other IDE's e.g. C#, C++ etc. C# would be the obvious choice after...

Needs to be =DLookUp("Course_number","Qry_Courses","(timeslot = 'W 8:30 - 10:20' or timeslot = ‘MW 8:30 – 10:20’) And room= '0AN70' and term= 'FC'")

I would say its the other way round. Q1 is the crosstab, Q2 is based on Q1 and includes new columns that sum specific columns created in Q1.

You can add a description to each query (right click =>properties.) You can show the descriptions if you like e.g. if you are looking for a particular query (right click at top of panel => view => details)

You can hide queries/table etc. You can also group queries/tables etc and also hide the groups.

This probably works too: If myString Like "*#*" Then myString = UCase(myString) End If

Maybe: If myString Like "*[0-9]*" Then myString = UCase(myString) End If