Could some body give me advice. I'm going to implement program working in real time withing working hours, i.e 9am - 5 pm. There is a database of materials including parameters of materials which are changing all the time. I have no problem with database and visual interface. The barcode in workshop will send a volts value to the desktop in a processing room. There will be a small network. The program with database will run on the next desktop. So for example the barcode value is being received from the workshop. Then this value must be sent to the next desktop where program with database is running. So how to find best solution? Shouid I use a timer control or to listen a port when barcode value is received and then refresh the database?..
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
real-time VB6 program
- Thread starter olegflute
- Start date
ArtieChoke
Programmer
Either of those methods can work. The "best" solution is one that you can understand and maintain - it doesn't really matter how you do it.
One way to look at it is to figure out your constraints - mainly time and resources. If you have all the time and people to work on it that you want - you could explore using windows sockets with an ActiveX server program, for example. If you need it done yesterday (like most of the projects I know of! ;-), keep it simple - like dropping the value in file on the LAN and checking for it periodically.
It just depends on your needs. Simple is usually the best choice unless the situation demands more complexity. In your case, going to the trouble to set up inter-computer communication isn't really needed, unless you want to learn how to do it. You could always use this project to learn something new.
One way to look at it is to figure out your constraints - mainly time and resources. If you have all the time and people to work on it that you want - you could explore using windows sockets with an ActiveX server program, for example. If you need it done yesterday (like most of the projects I know of! ;-), keep it simple - like dropping the value in file on the LAN and checking for it periodically.
It just depends on your needs. Simple is usually the best choice unless the situation demands more complexity. In your case, going to the trouble to set up inter-computer communication isn't really needed, unless you want to learn how to do it. You could always use this project to learn something new.
You know that "real time" has a very specific meaning in programming?
It's usually used to describe programs like airplane control software, nuclear power plant control systems, etc. These are systems which absolutely positively must respond within a few milliseconds of an interrupt.
In your case, it's more of a data logging system.
Chip H.
If you want to get the best response to a question, please check out FAQ222-2244 first
It's usually used to describe programs like airplane control software, nuclear power plant control systems, etc. These are systems which absolutely positively must respond within a few milliseconds of an interrupt.
In your case, it's more of a data logging system.
Chip H.
If you want to get the best response to a question, please check out FAQ222-2244 first
- Status
Similar threads
- Question
