DonB
|
| Posted: 07/01/2002, 11:29 AM |
|
I've been having all sorts of trouble trying to load memo fields onto a
form, update them, and save them to the database.
The data fields appear to get updated out of position, meaning (for example)
a date field gets stored to one of the memo fields.
After much experimentation, I have concluded that the "Cmd" object is
getting clobbered. Along the way, I also discovered that CCS does not like
it when you change a field to memo from another type - the code does not
track and the places the field is used with a "type" designation such as
"CCStext" do not change to be "CCSmemo".
The Cmd object seems to get confused if there are itervening non-memo fields
separating the memo fields. I had date-memo-date-memo-date-memo in sequence
on my page. Invariably, one of the date fields would get stored in one of
the memo fields.
I finally was able to build a correctly-functioning page by using the Record
Wizard instead of the Application Wizard. I placed three memo fields,
compiled and tested is with successful updating.
Then I added the date fields. This broke the page - it wrote dates into the
memo fields.
So I then moved all the memos to the end of the page. Now the page seems to
work. Dunno why. I guess that Cmd has some sort of a problem figuring out
the index to the memo fields if they are not adjacent. Maybe this is
related to the fact they are constructed as "parameters" in byte-arrays
(looking at the code, the memo fields are handled this way instead of
in-line values in the UPDATE query). This mechanism is, of course, an ADO
requirement to enable it to pass large strings back to SQL Server.
So, be careful how you use memos.
don
|
|
|
|
|
|
