Search results

Sure, understood. I was fishing for a reply along the lines of "in my experience, things can start to lag around x number of records for a setup like that." Appreciate your responses though! Have a great one.

I've got a "visit tracking" db developed for our medical office. Each area has its front end interface that connects to the back end on the server and the Front Desk, MOAs, RNs, MDs, and Pharmacists all use it to alert each other to where the patient is and needs to go. We add somewhere between...

It reads off of an already existing text box that shows the minutes elapsed (DateDiff) in whole numbers, thus the rounding. It was a quick-and-dirty way to get on with the project that I'm sorting out better methods for now. Indeed, I do want each front end to alarm independently, so I believe...

Brilliant! I didn't realize a split db could also have FE tables. That sounds about perfect. I'll go look up how to do that and I think I'll be set. Thank you sir!

I haven't played around with the exact timing and how it works with access rounding the time - I just threw the 2min thing in when I was building it as "good enough" for then. Now, I'm in the final stages of polishing this thing up, and it just feels sloppy. Would rather have a definitive...

Hello folks, Cooking up a "Visit Tracking" application in Access (2007-2016 format). Each area has its own Popup form: -Front Desk -Nurse -Doc -etc... 1. The front desk creates a visit, and it appears on the Nurse's form 2. The nurse rooms the patient, marks which doc and room, and the visit...

I've always wondered that, thanks for the explanation. In my efforts to troubleshoot, creating a referenced control didn't seem to make a difference but I shall endeavor to do that in the future. (I assume it makes no difference that the control is marked not visible.) Thanks very much for...

Please forgive my persistence but I'm not sure I know what you mean. Is it not opening for you? I'm always looking to improve - to learn the proper way of doing things and avoid bad habits. I would greatly appreciate any advice you would have the time and inclination to offer.

Thanks isladogs - but I wasn't even sure WHAT I was looking for. I could be looking right at what I need and not know it. That's a very nicely polished demo db you have there, though! I can see why you're so quick to share it. Thanks! I found a specifically helpful answer here...

Howdy you Access experts, I'm having a devil of a time googling for this solution, I think because the terms are so mushy (or maybe I don't know the right term to use). If code (ran on a timer) finds new records on the backend db, I want to give focus to the frontend Access Form -the form will...

I wish I could give you more than 1 Thank. I'm a little ashamed I didn't work that out myself - I feel like I should have known that. Just for my own understanding, though, can you tell me why the exact same line worked on the FRONT DESK form without the 'Me!'? In any case, I'm deeply...

The visitID is the key field, passed to the form through a query in exactly the same way (I thought) as another form/query on which this works just fine. I can't for the life of me work out why it works on one but not the other as they are designed the same.

Understood. I was doing my best to type a clear and concise post that would alleviate such concerns. It's not my style to spam a bunch of posts when I have nothing to offer. I subscribe to the "two ears, one mouth" approach, usually finding answers by searching. Unfortunately, this db is on...

Thanks for the idea! But the visitID is a key field and this will only be run on existing records, so I don't anticipate needing null handling at all.

I would greatly appreciate some help on this error I'm getting: Run-time error '3075': Syntax error (missing operator) in query expression 'visitID = '. In the linked database, this code runs on the click event of the UPDATE cmd button: DoCmd.OpenForm "frmUpdate", , , "visitID = " & visitID...

Steve, I registered an account here just to thank you. I realize it's bad form to resurrect threads but the content is still quite relevant in 2019, and a hearty THANKS is in order here. Saved me a lot of time!