DMXzone Database Updater ASP Support Product Page
In progress
After updating record and data refresh, there are lots of spaces in my form fields
Reported 28 May 2014 04:50:16
3
have this problem
28 May 2014 04:50:16 Steve Skinner posted:
My update action/executor seem to be working, but something strange is going on. When you click into an empty spot after your text in a form field, the cursor always drops into the first available spot, usually right at the end of the last work - because the field the has no characters after that. However, after doing an update, the same form field values now appear to be fully populated with spaces through the entire rest of the space in the form field. I assigned a trim formatter to one of the fields, and it does seem to keep that under control, but I am wondering if I have to do this on every form field??? Is this normal behavior for the updater - filling in the remainder of the form fields with blank spaces?
Replies
Replied 28 May 2014 09:01:58
28 May 2014 09:01:58 Teodor Kuduschiev replied:
Hello Steve,
What is the database that you are using and what is the field type you are storing the info into?
What is the database that you are using and what is the field type you are storing the info into?
Replied 28 May 2014 13:39:40
28 May 2014 13:39:40 Steve Skinner replied:
SQL db and the fields are varchar
Replied 28 May 2014 13:42:00
28 May 2014 13:42:00 Teodor Kuduschiev replied:
Can you please send me a link to your page where i can see what is the data that is being sent to the db?
Email:
Email:
Replied 28 May 2014 13:53:25
28 May 2014 13:53:25 Steve Skinner replied:
Just sent it to you.
Replied 29 Nov 2014 20:50:51
29 Nov 2014 20:50:51 Tommy Nielsen replied:
Hi Steven
I have the same problem. Did Teodor come with a solution for this?
Best regards
Tommy Nielsen
I have the same problem. Did Teodor come with a solution for this?
Best regards
Tommy Nielsen
Replied 29 Nov 2014 22:42:46
29 Nov 2014 22:42:46 Steve Skinner replied:
No. According to them, this is not something they can solve. Read up on this thread.
www.dmxzone.com/support/22084/topic/59888
In short, you just have to go into the connections file and change all type 129 to type 200 (manually) and you will need to do this every time the connections file gets updated.
www.dmxzone.com/support/22084/topic/59888
In short, you just have to go into the connections file and change all type 129 to type 200 (manually) and you will need to do this every time the connections file gets updated.
Replied 30 Nov 2014 11:34:48
30 Nov 2014 11:34:48 Teodor Kuduschiev replied:
Hi Tommy,
we are aware of this and this will be fixed in the upcoming update.
Steve,
It is not something we can't solve, and this is not a problem in our extension, that should be improved. We will have to "hack" the NOT-UPDATED-FOR-10 YEARS ADO CODE, as it reports the data types of the modern databases WRONG...
And this requires an update. As i explained this will be fixed in the upcoming update.
we are aware of this and this will be fixed in the upcoming update.
Steve,
It is not something we can't solve, and this is not a problem in our extension, that should be improved. We will have to "hack" the NOT-UPDATED-FOR-10 YEARS ADO CODE, as it reports the data types of the modern databases WRONG...
And this requires an update. As i explained this will be fixed in the upcoming update.
Replied 30 Nov 2014 14:46:00
30 Nov 2014 14:46:00 Steve Skinner replied:
Thanks for the clarification. I obviously misunderstood your post on the other thread I linked to. Please understand I wasn't saying anything negative about DMXzone's position on this. I understood that this wasn't a problem with your extension and I have been fine with doing the manual update, but if you guys can figure out a way around it, then that's even better!