| Author |
 Topic  |
|
|
filf
Yak Posting Veteran
67 Posts |
 Posted - 07/27/2001 : 12:21:25
|
Hello,
I am having a problem related to the use of the following ole automation stored procedure:sp_OASetProperty
I am trying to set a variable of dType varchar 2000. When I call this sp, to set the property to the value of the variable, the SQL Server datatype is converted into a Visual Basic datatype, converting my varchar 2000 to string 255 causing unwanted truncation.
Does anyone have any idea how I can actually get around this problem? It would be great to get a quick fix for this.
Thanks in advance.
Edited by - filf on 07/30/2001 04:33:21 |
|
|
nizmaylo
Constraint Violating Yak Guru
USA
258 Posts |
Posted - 07/27/2001 : 12:30:51
|
Can you post the code?
helena |
 |
|
|
filf
Yak Posting Veteran
67 Posts |
Posted - 07/27/2001 : 12:43:22
|
If you look in BOl for the stored procedure : sp_OASetProperty
there is a link at the bottom about data type conversion. This is my problem I would like to know how I can solve it, has anyone experenced this in the past?
|
|
|
|
filf
Yak Posting Veteran
67 Posts |
Posted - 07/31/2001 : 11:13:31
|
Has no-one tried to send a mail longer than char(250), or is everyone just hitting the same brick wall that has stopped me, I am trying a workaround and if it works I will post it, has noone else come up against and or solved this string truncation problem.
There must be a way round it, I have a theory which I am currently testing, is there anyone out there with superior knowledge of visual basic data types?
|
|
|
| |
Topic |
|
Truncation Problem using OLE automation SP
