Recent content by prley

thanks much txgeekgirl exactly what i was looking for.

I too was experiencing this on a shutdown form I started using to force users to shutdown. It was hidden form. I added code to the unload event of the main form to see if this form was still loaded and if so to issue a docmd.close to the open form. Now It's not firing the load event. Go figure.

+1 Like Old Man Devin said just issue the code above on all of your report open procedures. Then change the acToolBarYes to acToolBarNo to hide the menu again in the report close proc. I had to do this to all my reports that use the preview since I didn't want the user to see the ribbon anywhere...

Sorry to bring an old thread back but as usual I found exactly what I needed in the above function to find the first day of the week for a given date. Thanks pbaldy!!! Works like a charm. Otherwise I was going to subtract a number of day based on the day what the day of the week function...

Quite true. Sometimes it rears it's ugly head when you have multiple users/databases. You might want to stat considering using a versioning/auto update utilitiy. Bob Larson has made a great tool. It's a little difficult to get going but once you have it running properly it's a beautiful thing...

Nice find. I'm a little old school and the instring/replace function weren't around during my initial development years so I forgot all about these functions. Sure saved me a lot of long hand coding for my particular situation. Again this site comes through even though this is quite an old...

If I understand your question. Your putting a new version of the front end out but it still looks back at your local drive for the data instead of the new location. I usually move the back end database pn my local machine when I put a new version in since I don't usually do that many changes...

Thanks it didn't occur to me that I can just drag sub reports into a main one. This should of been a no brainer but I hadn't had a problem like this to solve until recently and your comments made a light bulb go off in my head. Go figure. Got to remember OOP. Sometimes I try to do things the...

also after you register it. make sure the dll is in the same location as displayed as in the example under the registry setting codebase. You can double check this in the reference window when you highlight the code library as in the instructions... "You may remember in the registry...

Did you check the table where the data is stored? Without more information about your form I can't help.

try looking at the property input mask on the field and set it to password. also check the table where it's stored to have the same property set.

On the properties of the report will show you the record source ie query. Unless you are defining the query in VBA of the report itself.

Maybe post the query and I'm sure someone will chime in. Since you getting output it's probably something simple like you said in the report design.

I would suspect the report design. You might have the record source property of the report set to the whole customer table. The record source of the report should be a query that uses the paramater your sending (str) it to identify the one record you want to print. I havn't used paramters with...

I was wondering if that was the way it worked. So the file association comes into play. Not a very good name for the function though unless it was intended primairly for different use.