Search results

Firstly, thanks for all of those who suggested various causes and fixes. The issue was finally resolved and it was one of those very annoying ones where the only symptom I was seeing that Nz stopped working but the cause was larger. It seems that something happened during the latest software...

Not the cause here, unfortunately. It's a field called 'Approval' in a table. I just tried recreating the control, in case there was something 'off' with the original, but no change. I'll find some workaround, it's just going to take time.

Sorry, missed this response. Yes and yes. As far as I can work out, txtApproval is not null but also has no value. If I try to assign a value just before the error line, I get told I can't assign a value to it.

Thanks for the feedback, gentlemen. The version, etc. is as follows The references are as follows

One of the downsides of working for a big corporation. Access is looked down on as a bit of a childish application. IT want us to switch to something they will build, but the department manager won't allow it as it would slow down enhancements (and take years to build). Because IT don't control...

Found a way around part of the problem. This code If Not IsNull(txtApproval) Then txtOrigApprover = IIf(IsNull(txtApproval), "A", "B") End If MsgBox txtOrigApprover MsgBox txtApproval sets txtOrigApprover to "B", suggesting that txtApproval is NOT null. However, the...

Hadn't seen that way of doing it before. Thanks. Unfortunately, same error message.

Thanks. I've requested it but it's company wide so won't happen. I was, effectively, told that I have to work with it.

I can't see this specific problem described already, here or via Google, but I apologize in advance if I was just searching using the wrong terms. Many of the Access databases I look after include some variation of If Nz(txtApproval, "") <> "" Then Where Nz is used to replace a Null value in...

I asked but he wasn't very forthcoming. I get the impression whatever he did was either embarrassing (and he doesn't want his boss to know) or he doesn't know himself. His explanation was that "it was a permissions thing". I pushed for him to expand on that and he just said I the permissions on...

In case it's of any use to anybody else, I found the problem but not the cause. The file in question had some property which was preventing it from being deleted using the method I was trying. I had the person who produced it remove and recreate it and all then worked, form my end of things. I...

Apologies to ebs17 and Gasman. I didn't see your responses before I last replied. I can confirm 100% the line causing the problem is being reached and it's the the one that's meant to kill the file. Bennet: I think you're right. I added extra error handling and the result is "Error #70...

Thanks, both. DocMan: DoEvents didn't help, sadly. MajP: Did as suggested and the same thing happened. The code gets to the 'kill' line, then nothing happens to the file I'm trying to delete and the code stops running.

I'm running the following line of code in a module kill "Q:\Auto\Used Data\CasesCurrentlyBeingImported.csv" It doesn't produce an error message, but doesn't do anything. The module ends at that point and exits out. I thought it was a permission thing, but if I insert a break point just before...

Finally able to check the guy's machine (he was on vacation). From what I can see, everything in the Date and Time settings is identical to my own PC.

Will do. Always annoying when this stuff comes up, since IT insists we all have the same build and setup on our machines

I did check that. Thanks.

Thanks for the response. So, this single user could have some kind of regional setting on his computer which doesn't include a time component?

This one sounds a little odd, I know. I have a table in an Access 2010 db, in which one of the fields has Date Type 'Date/Time'. The format for the field is 'General Date, which includes a time component. The field is auto-populated when a user enters a new record. Of the 26 users, 25 have...

Thanks. I've found a workaround for it, but have no idea why it's working when the previous method (which has been in place, unchanged, for over five years) has started throwing up these errors. The original method had Db.Execute followed by a SQL statement which included a passed variable...