I would think for code changes (fixing bugs, etc) the easiest thing to do would be to pass out a new .exe file to replace the previous one. Users would just have to replace their existing .exe value with your new one.
On the other hand, to be more like a true patch system you could code your .exe file to be prepared for patches by checking for updates to any functions by checking for them in a specific location (like a DLL file), and then applying those changes during runtime. However, I think this might be a bit too advanced for you if you're still just learning DBPro.
'Just one game,' they said, and started to play. That was yesterday.
Dual Athlon 2.0/1GB RAM/GeForce Ti4200-128/Win2000 Pro