Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 5 of 5 total |
Notify other open Apps that a table has been updated and they need to refresh their copy. |
Sun, Mar 1 2020 1:49 AM | Permanent Link |
Ian Branch | Hi Team,
I'm sure this is an eternal problem.. I have multiple lookup tables and up to 20 users may have them open through various apps at the same time. Is there some mechanism where is User A updates Lookup table A, that the Apps are advised and they update/refresh their data for Lookup table A? Regards, Ian |
Sun, Mar 1 2020 4:24 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Ian
>Is there some mechanism where is User A updates Lookup table A, that the Apps are advised and they update/refresh their data for Lookup table A? Not built in, or if there is I never found it. You could look at building in some sort of multicast system (UDP) to notify apps they needed to do a refresh or a background thread which just checks for changes and syncs if it finds any - you'd probably need to build an update timestamp into the lookuo tables for that. Part of the problem is that ElevateDB (and DBISAM) allow both c/s and f/s access so there's no common place to do the notifications. Can you describe the usage a bit more. I'm just wondering if I could do anything sneaky with TnlhTable. Roy |
Sun, Mar 1 2020 3:37 PM | Permanent Link |
Ian Branch | Hi Roy,
I wouldn't stress it. It was just a hope. By way of explanation, there is not much more to add. To be a little more specific, consider say 10 users with App A open logging in, adding and processing Jobs. Associated with the Jobs is the Customer table where Customers are added fairly regularly during the day. ATT when a Customer is added, an App has no way of knowing nor does the user so during the next Customer lookup, unless the Customer Table is refreshed the new Customer may/will not be visible/available. >>...""You could look at building in some sort of multicast system (UDP) to notify apps they needed to do a refresh or a background thread which just checks for changes and syncs if it finds any..." OK. That's out of my league/knowledge base. Hmmm. Re-reading what I have just written, perhaps if I forced a Customer table refresh every time a lookup was called for.... Don't know what the performance hit would be. Regards, Ian |
Mon, Mar 2 2020 2:50 PM | Permanent Link |
Steve Gill | Hi Ian,
<< I'm sure this is an eternal problem.. I have multiple lookup tables and up to 20 users may have them open through various apps at the same time. Is there some mechanism where is User A updates Lookup table A, that the Apps are advised and they update/refresh their data for Lookup table A? >> I do something similar to this using triggers and UDP. It works quite well. You can either send out a UDP broadcast, or send a UDP message directly to each workstation's IP Address. = Steve |
Tue, Mar 3 2020 5:52 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Steve
>I do something similar to this using triggers and UDP. It works quite well. You can either send out a UDP broadcast, or send a UDP message directly to each workstation's IP Address. From Ian's post <<OK. That's out of my league/knowledge base.>> Its also something I've never done. Any chance of you whipping up a small demo? Roy |
This web page was last updated on Sunday, May 19, 2024 at 08:46 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |