Recent content by plog

Apology and thanks accepted. When you want to hardcode SQL inside VBA you should first get your SQL correct by using the query designer. That's the tool to use to debug your SQL. Once it works you can extract the SQL and paste it into your VBA code.

1. You make it so much harder to debug SQL when you have it in VBA. It's like a game of telephone you have to play to get to the SQL. What exactly is the SQL in sQry? 2. Why is there an alias in that thing? That makes it even more harder too. If there's only one datasource in the FROM...

Ugh.

Big picture--the thing you are doing wrong is you are treating Access like it's a spreadsheet. Here's your fields: That's not how databases work. In that 1 screenshot I see 2 huge errors: 1. If you are going to add/subtract fields together (like you do to all those _Disbursement and...

Never use FIRST, LAST, DFirst() or DLast(). They just don't work like you think they do. You're post drowned me in code and irrelevant details, so I am not clear how to help you specifically, so I will in general. In general, instead of LAST in a query, you should build a subquery using MAX...

Why don't you have one of these tables for each dealer? Why not then a table for each product? Because you put that data where it belongs--in a field. You are able to handle multiple dealers and products in the same table because you have fields that allow you to differentiate what product...

My advice is dive in. Seems like you have a good enough grasp of things to get started. Open up Access and set up the tables and fields you think you will need. Then complete the Relationship Tool in Access, expand all tables in it so you can see all the fields, take a screenshot of it and...

It sounds like you know vacancies and then you assign candidates. So I would stick with the main form being based on (one record from) Vacancies and the subform based on (many records from) Candidates...

What's your real world workflow? 1. How do vacancies come about being entered in the database? A bunch at a time or just one every so often? 2. How do candidates come about being entered in the database? A bunch at a time or just one every so often? 3. Who enters vacancies and candidates...

Yes, sort of. Broad strokes--I don't do this once-- I build a process to do this and make that process airtight. Once the process is built it, I run it one final time and have full confidence the data will migrate succesfully because I have worked out the kinks and fixed all the data. That...

GpGeorge got it right in his first post -- you shouldn't be doing this. You can achieve what you ultimately want, but this is not the way to do it. You don't store both age and date of birth in a table because age can be calculated off of date of birth. Further, age tomorrow isn't guaranteed...

I've played this game before many times on this site, but willing to do it again for you: I strongly suggest you use autonumbers and forget this ultimately useless amalgamation you think is the right solution. Here's where you say--"But we need all that information crammed into a string...

You don't need the _1 tables in there, you only need each actual table in there once. However... 1. Remove the _SuccesfulID fields from VacancyCandidate_Tbl and replace it with a Yes/No field called Success, default it to No and if they are successful change it to Yes. You now know if they...

I've got the right help, but not help you are going to want to hear--I think you have set up your database tables incorrectly. The little we have to go on raises a lot of red flags. The Detail section doesn't use any data from the report. It uses DSums which have their own data source...

You need another table---VacancyCandidate. Since a single vacancy can have multiple candidates and a single candidate can go to multiple vacancies you need a table to sort all that out. This is what that table looks like: VacancyCandidate vc_ID, autonumber, primary key vc_DateTime, datetime...