Recent content by Nightowl4933

Hi Minty, I do have a separate table for the Authority - and the Authority field in the Applications table is a lookup to it. I've just (literally) sorted that bit, and I'm with you on changing the lookup field in the applications table. Could I do this with a simple update query for that...

I've changed the search criteria field from a Lookup to a ComboBox where I've added the values, but the problem persists. I get either a Run-time error '3464' data mismatch error if I use the text value of the field, or a 'Enter Parameter Value' if I use = comAuthority.Column(1) as the value...

Hi guys. Sorry for not responding sooner. OK, I can upload the front end of the database, but obviously you won't be able to see the data. Would this be enough to get an idea of where I need to go, please? If not, I could upload the pre-split db, but would request discretion :) To be more...

I tried to use both options, because I get the problem with using a Lookup. The trouble is, whichever option I decide on, there's always an error! When I use the numeric value, I get this error. When I use the text value, and include the resulting string in quotes, I get a different error!

Plog very kindly provided a solution to a problem I had with multiple search criteria, but one of the options is causing me a bit of a headache as it doesn't work - and i've only just noticed it! Basically, I'm using a series of If... Then... to concatentate a search string in to a workable...

A bit of an update... I've tried to run a simple query based on the same criteria, and it seems to work. I've used: SELECT tblAllApplications.PlanningAuthority FROM tblAllApplications WHERE (((tblAllApplications.PlanningAuthority)=1)); ...so I'm going to try to step this up to the full...

OK, so this has developed a bit of a bug, and I don't know how... When the database was 'released' it was split, with the back end on a server. I'm pretty sure it all worked wonderfully, but playing with it recently identified a flaw in my cunning plan, in that when one of the search criteria...

...but I would like to find a solution to this inconvenience... My database runs on the work's network and the tables are mapped to a back end database. I develop the database at home, so I was hoping to set up a directory structure so any changes I make to the front end will only need me to...

That's exactly what I want! I knew I was complicating it too much! Thanks again, my friend - and thank you, plog. Pete

Hi plog, Example database attached, as requested :o All (!) I would like is a single column of calculated dates (i.e. Z showing the combination of E and X), that can be sorted as a date and in order. It's my intention to use conditional formatting in a form to highlight those dates that are 1...

Nope, everything's fine - but not what I want to achieve! I would like a field that combines these and can be sorted by date order.

'ere you go...

E: CDate([Expiry]) and X: DateAdd("yyyy",[Limit],[Granted]) I was using the wrong date in Column 1 - sorry. Pete

I can see why this is a problem! I've split out the different date calculations and this is what I've got left. I'm a bit confused at some of the calculations, though. The top line show 12 years added to 22/06/2011 as being 22/12/2023 :confused:

Hi plog, The results of the calculation seem to be misleading me, then, because they all have [Granted] dates, and adding Is Not Null to tht field gives the same number of results. [Limit] is the number (Double) of years I want to add to the [Granted] date, but only if [Expiry] Is Null...