Search results

Anyone know how to trap (and of course supress) the default message when the input mask is violated. It doesn't trigger the form's Error event. Thanks

Looks like more trouble than it's worth. Think I'll just manually set a variable to the field size for each control that calls the code. Thanks guys.

I'm trying to query the properties of the control source of a field in a form. Specifically I want to interrogate the Data Type and the Field Size. I've gotten as far through the object model as: Me.ActiveControl.ControlSource But I cannot seem to srting together the right syntax to get it...

On second thought... I was just playing with the zoom function. Althought it's simple to implement, it doesn't leave you with much control or custimizability over the user's input. So I'll stick with my own method. Looks like there are advantages to doing it both ways. And yes, we're under...

Duh I obviously have special access keys disabled, so I assumed that the SHIFT+F2 would not work. But it does. Guess we all know what happens when we assume. :p Thanks.

My users have requested that I provide a popup textbox that gives them more room to enter text than can be provided in the smaller parent field in my form. I made a simple popup form that has one unbound field that allows text entry. When the user double clicks in the parent text field, the...

I'm helping someone implement user-level security on their Access 97 database, and we've run across an interesting snag. There are external Excel and Word documents that query the database for information through MS Query. I have set up the database to be access through a shortcut that links...

=IIf(IsError([FieldName]),0,Sum([FieldName])) Sometimes this works, too: =IIf(IsNull([FieldName]),0,Sum([FieldName])) Which one to use seems to depend on the underlying query structure, but don't ask me why.

That's a good point. I wonder if there's a way to trap that error and customize the error message... I've now had a chance to look at this. It triggers a 3024 error that is easily trapped in the Form_Error event.

You'd have to be kidding yourself to think there's any real security, but it comes down to the low-hanging fruit. In the end, all we can do is make it as tight as possible.

Thanks Autoeng. I've also heard of of making the tables themselves hidden within the backend, although I don't personally do that.

This is sort of getting off the topic, but the path to the backend is actually hidden by linking the tables in the front end directly to ther server rather than by mapping the drive on the user's system. If the front end is correctly restricted, the user cannot find the path to the backend from...

Actually, user-level security applied to the front end won't protect the backend. The backend is usually protected by operating system security. My reasoning was from a performance standpoint. I have heard that aside from being more secure, MDE files perform better. I'm guessing that this...

Has anyone ever tried setting up the backend of a split database as an mde file? It occurs to be that this might be smart, but I've never tried it or heard it suggested, and I'm thinking there must be a reason.

Yah, I've asked other developers this, and that's pretty much the concensus.

Does anyone know of a way to interrogate the name of the subroutine currently running? I just want to use if for my error handler, which messages the user as follows: MsgBox "OBJECT_EVENT - Error #" & Err.Number & ": " & Err.Description For each event, I overwrite "OBJECT_EVENT" with the...

Maybe I'm missing something, but that didn't work. I created an unbound textbox in the details section of the subreport. I tried multiple permutations, setting it to equal a constant (1), another control in the subreport, a control on the main report, and a control on the form that calls the...

I suspected as much. Guess I'll just write an error trap to replace the cryptic Access error message. Thanks, guys, for your help.

:p I was hoping for something a little more programatically robust.

Thanks. That's not really what I want to do though. I'd prefer to force the subreport to be visible (the headers and footers would show, but the details would be blank). It would save me a lot of monkeying around with the reports.