Using edit boxes on the main pages of your HMI screens is a bad idea. It doesn't matter whether you use DAQFactory or another tool. The problem is feedback.
(An edit box is a rectangle on the screen that you type new values directly into, an HMI is a screen or set of screens that allow you to control a real world device or at least view its status).
Let's say you have an edit box on your overview screen that changes the set point on the boilers. You type in a lower value into the edit box and then get distracted by your boss who wants a full accounting of your SCADA system expenses because they are too low. Unfortunately, you got pulled away before you moved the cursor away from the edit box. While you were gone, a coworker comes in and looks at the overview screen to make sure everything is ok. He looks at the edit box and sees you have a setpoint of 200C, but the system is showing things at 500C. He panics because something must be wrong, hits the Estop and shuts the whole system down. The boss, who was just about to give you a raise for saving so much money using DAQFactory instead of the expensive alternatives on the SCADA system, changes his mind because you just cost him down time.
So hopefully you see the problem. Edit boxes alone can cause current values to be misrepresented if the values are typed in but never submitted. Its even worse if you don't use the "Submit on Exit" option and a submit or set button instead. Just looking at the screen you don't know if the value is actually set without secondary feedback.
The better way to change values is with a popup. This is actually the only place, I believe, an edit box should be used. If you just have a single value to change, use a variable value component (or button, or descriptive text, etc), with the Set To action. This will create the popup for you. If you want to change several values or provide additional information, create your own popup and make sure and pop it up modally. This means the the window has to be dismissed before the rest of the program can be used. What this does is provide positive feedback that the value is changed or not. If the popup is visible, then the value hasn't been set. You can also create configuration pages that aren't popups, but they shouldn't have any real-time values being displayed. The user must dismiss the window, either saving or canceling to get back to the real-time display.
"But so many other Window's programs use editboxes..." Yes, but they are not real-time. They don't refresh the screen constantly with updating values.
So, only use edit boxes in a popup window, or on a screen that has no real-time display and has to be dismissed with a Save or Cancel type button.