Replies

Thanks for your help and explanation.

Everything seems to be working properly now.

So I need a second pair of ‘strDate’ variables formatted to mm/dd/yyyy for use in the where clause?

DueDate is a calcuated field in the report’s query. Do I need to re-format this to US too? I get pretty confused with dates, particularly the effects (or not of formatting) the ‘real’ date.

I’m using a form to try to set a date range on a report but it isn’t working correctly

This is the code that opens the report

strFromDate = Format(txtFromDate, “dd/mm/yyyy”)
strToDate = Format(txtToDate, “dd/mm/yyyy”)

strDocName = “rptReExamSchedule”

If Me.chkIncludeBefore = True Then
strWhere = “[DueDate]=#” & strFromDate & “#) And ([DueDate]=#01/09/2007#) And ([DueDate]<=#01/08/2008#)

Unfortunately I'm getting results for records with a DueDate of 05/04/2007

I'm in the UK and use the date format dd/mm/yyyy. I suspect this is something to do with the date comparison assuming American date formats.

Thankyou

I can’t believe how many times in the past I must have been into the page setup dialog without really noticing the columns tab. I think I’ve looked at at every property of the all controls and sections on your report but didn’t go to page setup!

Thanks again

I’ve just had a look at this and I can’t figure out how you get the continuous report to have two columns.

What (probably obvious thing) am I missing?

Is each user expected to have some level of expertise (even beginner) in all 400 skills?

If not, maybe you could use a popup form with a list box which would allow the user to select their skills (the list box would display skills from a lookup list and would only display those not already selected – over time, as the user adds more skills the list would get smaller). Once copied to the relevant table (say tblSkills – a child of tblPerson) the skill info could be displayed on a subform (as suggested by Hans) for the user to enter their proficency.

You could create a report (based on the layout of your original data entry form) showing all possible skills with ticks for those the user has provided information on.

The service pack didn’t seem to work but Mark’s utility did – problem solved. Thanks

Perfect

Had just decided to go for a series of update queries but was wondering about the concatenation.

Your cut down example makes it very clear. Thankyou.

Yes, it is being seeing as a two phase type of thing. The ’rounding’ of the coordinates produces more ‘possible’ matches. I need to keep those that were ‘exact’ separate.

I’m sure trying to ’round’ the values and compare them will take ages but I’m kinda stuck before even before I get to that bit. I really can’t think of the most appropriate way to deal with ‘a’ and ‘b’.

If I deal with ‘a’ first then the numbers of records needing the lengthier ‘b’ search would be less BUT it doesn’t seem unreasonable to just leap into ‘b’ and deal with the results of the function differently. ie. if collection.array has one item, write to field a, if it has more than one, loop and create a string and write to field b.

As usual, a huge thanks

Thanks, it seems to be behaving itself now.

I discovered as I ran it and missed out some changes, errors cropped up unpredictably at different points.

Why do the references need full qualification in this instance?

Excellent. I will probably go with a random autonumber key and maybe have a ‘date created’ to sort by.

Thanks, this all sounds too easy!

Seriously though, I really thought this was going to be a huge problem but now I’m confident Access is still up to the job.

Can you remember roughly how many users you had? The app I’m working on currently has 6-12 remote users entering around 6 records day. Ultimately this batch of work will amount to around 2000-3000 records, which will be added to an archive of 15,000 records (once I’ve sorted out the issue in post 559,230).

Thanks everyone for your prompt replies.

Hans, I think your suggestion looks the most promising.
Of the two options you describe, which do you think is best ?

Mark, there are effectively two fields that could form the key (the ExamRef and Date) but I’m using the autonumber to link to a child table – my understanding is composite keys are a pain when child tables are involved – have I got this wrong?