Search results

Those 3 numbers create a sequence that will never be duplicated. There will only be one front end with Site # 1 Location # 2 and SiteWorkStation # 3. If it's sound and logical I don't see the need to overcomplicate things. Let me put things into perspective. I have a small market in the Bahamas...

I use the autonumber for the site and location table. Then I use incremental numbers for the work stations based on the # of licenses at a given location. Super simple. Haven't had any issues yet. Nonetheless, I can be dead wrong here.

I'm really appreciating your insight on this. So I have 3 tables describing a company. 1. Site_T: this is the main company's name e.g. Walgreens Pharmacy 2. Location_T: this is the branch name e.g Walgreens Pharmacy - Universitt Drive, Ft Lauderdale Florida 33314 3. SiteWorkStation_T: this is...

They all share the same BE. Queries with unique IDs keep financial data private. The reason for this is pharmacy management software is pushing towards interoperability. For example right now refill transfers is a manual process (in the Bahamas at least). Having pharmacies on the same database...

Hi Pat! So every license paid comes with one "unique front end accde file". All paid subscribers can use the application simultaneously. The only time a restriction takes place is when an unpaid user tries to use a copy of a unique front end accde file. So, let's say I have 10 paid subscribers...

My point is that your "thoughts" do not contribute to the discussion whatsoever. So next time try not to be so impulsive and keep your thoughts to yourself. Unless that is you plan to give your input on the topic at hand. Do you have anything to contribute in this regard?

refer to my previous comment: @The_Doc_Man I want to ensure I understand your concerns as I can tell you understand access/database design a whole lot better than I do.

@KitaYama it was a joke and I'm certain @The_Doc_Man didnt take it as an insult. If he did that was not my intention. Him and I were having dialogue of which I thanked him for his insight on the matter. No need to come here and make things awkward. Please dont twist my words into something it is...

I'm now at the point of considering cost between the synced sharepoint folder and remote desktop services.. then compare the risk and benefits.

I consulted with our robot overlords (chatgpt). 🤣 @The_Doc_Man it seems as your concerns are valid. But I'm still not too convinced of a major issue here. Here is our conversation: https://chat.openai.com/share/6e6a5ebd-0049-40dd-a530-2944e0cdd685

From what I understand about synced sharepoint folders, they allow users to continue working on files in its folder even if the internet is down. Therefore, internet connectivity shouldnt be an issue. Furthermore, only one user should be editing the unique front end accde file anyway. Therefore...

I will keep that in mind. I don't know much about PHP though. Would be interesting to see how it works.

Thank you so very much @MsAccessNL for your kind words! I'm happy you like it! :)

MsAccessNL you're absolutely right in regards to slowing down the performance. This is why I increased the interval to every 10 seconds (10,000 milliseconds). I noticed this last night and changed it. It seems to be working fine now. Good eye sir! Also, I have a few thoughts about developers...

Hey guys, take a look at the image attached. I hope it gives you all a better understanding of what I've done. If there are any kinks in my armor, please feel free to call me out on it. I greatly appreciate all your criticism.

Just to add, I also track the number of users currently active if by some chance the "pirates" bypass this. I also add an sql_update statement to add the number of users that are successful in logging in (when they click the login button on the login screen, this will happen). Once it's <>1...

I can register the shutdown with an sql_insert statement into a table that counts the shut down event, at what date/time and on what computer. Im not sure I understand your second question. If the client (paid user) crasher unexpectedly then the mechanism doesnt happen. When the client tries to...

I did not think of that. Thank you so much for bringing this issue to light. Maybe I can do a control based experiment with this to see just how much performance I'm losing. As mentioned, the main purpose of keeping the accde file in the synced folder was not entirely about security. It was more...

I suppose I can create a table to monitor this sort of behavior as well. Every time this mechanism kicks in I can be made aware of it. Perhaps a counter against each customer name? Any advice here?

No but its hard to imagine someone that would endure that level of inconvenience. To log out of the app then log back in during normal working hours is a bit impractical. Also, I mentioned in the initial post that it also depends on the customer you have. My customers are pharmacies of whom are...