I've got a puzzler here. In a VB6 database application running on SQL Server, one of my forms has a bunch of textboxes (as well as datacombos and checkboxes) bound to an ADO control, each populated with a different field from the current record. Many of these fields are optional and often empty.
On all computers using the application save one, when a field is empty, it remains empty. On one of the computers, a space is automatically inserted in each empty field. Note that at this point, there is still no space in the database, but somehow it does put one in every empty field on this particular computer (and obviously, once the user saves a record he's created or edited all those spaces go into the database as well).
I'm positive it's nothing in the program or in the database that's doing this, and the problem seems to be isolated to that single computer. My first thought is "something in the Windows settings" but I don't have a clue what. Anybody have any ideas?
"Much that I bound, I could not free. Much that I freed returned to me."
(Lee Wilson Dodd)
On all computers using the application save one, when a field is empty, it remains empty. On one of the computers, a space is automatically inserted in each empty field. Note that at this point, there is still no space in the database, but somehow it does put one in every empty field on this particular computer (and obviously, once the user saves a record he's created or edited all those spaces go into the database as well).
I'm positive it's nothing in the program or in the database that's doing this, and the problem seems to be isolated to that single computer. My first thought is "something in the Windows settings" but I don't have a clue what. Anybody have any ideas?
"Much that I bound, I could not free. Much that I freed returned to me."
(Lee Wilson Dodd)
