Jump to content
Posted 18 June 2018 - 09:46 PM
Posted 21 June 2018 - 05:55 PM
What exactly are you trying to achieve with this ?
If it's a matter of numerical sequence for documents and only two locations are involved how about one site uses odd numbers and the other even ones ? You could then tell at a glance where any file originated.
Posted 21 June 2018 - 05:58 PM
Posted 21 June 2018 - 06:43 PM
In effect what you are saying here is that whenever anyone tries to file some kind of report, whichever of your two buildings they are working from, you want to have some kind of system in place which inserts a number one larger than whatever number was on the previously filed report? And in theory your previously field report could have been done at either the station typing a report now, or the other station? I'm just checking that we've properly understood what you want.
Have you ever done any sort of programming? I'm wondering if a solution might be possible using a raspberry pi as a "server", not a server holding anything big or complex, just solely their to control the iterating of your numbers, and to send info back and forth from the buildings about what the most recently filed number is.
P.S. how often are you doing this. how many reports per year approximately, knowing this will be very important when it comes to choosing the form to store the number in so as to avoid integer overflow.
Posted 21 June 2018 - 06:46 PM
Posted 30 June 2018 - 05:39 PM
Edited by rp88, 30 June 2018 - 05:42 PM.
Posted 30 June 2018 - 05:48 PM
Could you state whether my understanding in post #4 is correct? The 600 runs figure is useful, you could go for many decades before having any difficulty with programmatic representations of that kind of number but I'm still unsure as to whether I've understood exactly what your current method is supposed to do, what are the desired inputs, outputs and processes. I'm also unsure what you do or do not know about programming and networking. In the absence of other information one wonders why you wouldn't just log all callouts at one station as StationA_X where X is your number and all from the other station as StationB_X. One also wonders if when automating the handwritten number iteration, due to the higher workload expected when operating two stations, might as well involve automating other aspects of whatever your process entails.
Posted 30 June 2018 - 05:51 PM
Posted 30 June 2018 - 08:26 PM
Well, if the objective is strictly to have two locations able to grab, "the next number," such that they don't overlap one simple way to do that is via a spreadsheet under Google Docs, accessible to specific individuals at each site (or, if it's safe to be "way open" create a Google account that anyone that's part of the team can access), and always snag the next unused number from the spreadsheet.
Of course, I'd have other fields, too, like date, who snagged the number, etc., that need to be filled in by the snagger.
If you've been doing this by hand in one location, and pretty much plan on doing something entirely at one location or the other, other than needing sequence numbers shared by both, then you can use a spreadsheet that can be accessed by either location for that purpose.
Personally, I very much like the plan mentioned earlier where Station A would have only even numbers and Station B, odd. Even better would be to make the sequence numbers "multi-part" much like an SSN. Three digits for the station as the first three, followed by, for instance, YYYYMMDD-HHMM, snagged when the report is generated. Codes make a lot more sense with fixed parts for whatever element could change or be expanded (e.g., station ID), but with something that can be generated without any concern for what any of the others have done for what follows it, and what that is can be determined based on your needs. I just used YYYYMMDD-HHMM as an example because it's dead simple to acquire.
Brian AKA Bri the Tech Guy (website in my user profile) - Windows 10 Home, 64-Bit, Version 1809, Build 17763
Travel is fatal to prejudice, bigotry, and narrow-mindedness, and many of our people need it sorely on these accounts. Broad, wholesome, charitable views of men and things cannot be acquired by vegetating in one little corner of the earth all one's lifetime.
~ Mark Twain
Posted 01 July 2018 - 05:59 PM
I am curious as to why this adminstrative problem is landing on your shoulders. I am familiar with the concept of volunter/ part-time firemen as we have them in the UK as a quick reaction team for smaller communities, but the stations and equipment are supplied and funded by the national fire service as are the administration systems.
You mention 'town ordnances' so presumably your local town or county or state system is responsible for your administration, so why are you having to do this ?
Posted 01 July 2018 - 06:42 PM
Our town is very small and independent. We have no IT department and I'm currently in college studying networking. I'm not real savvy with programming and things of that nature yet. They will buy all of the stuff I need; just some things I look to learn such as this particular issue I have.
Posted 02 July 2018 - 06:26 PM
Fair enough and I appreciate your problems, I am currently trying to do some small scale circuit and PCB design, something I haven't done for about 25 years. Rusty or what ?
Your answer then is to keep the solution as simple as possible. If my 'odds and evens' suggestion is too simplistic for your requirements then seriously have a look at Google Documents as suggested by Brian. This can be set up from entirely private - one user only - all the way through to quite large groups having access to all the documents in the system. Google's help isn't bad either, they do after all want you to use their 'cloud'.
While this will mean that your record makers will have to move away from 'pen and paper' to using computers, and this may call for some training, it will not call for any programming skills on your part.
0 members, 0 guests, 0 anonymous users