Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

Our new SQL Server Forums are live! Come on over! We've restricted the ability to create new threads on these forums.

SQL Server Forums
Profile | Active Topics | Members | Search | Forum FAQ
Register Now and get your question answered!
Save Password
Forgot your Password?

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Truncation Problem using OLE automation SP
 Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

Yak Posting Veteran

67 Posts

Posted - 07/27/2001 :  12:21:25  Show Profile  Reply with Quote

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

Constraint Violating Yak Guru

258 Posts

Posted - 07/27/2001 :  12:30:51  Show Profile  Reply with Quote
Can you post the code?

Go to Top of Page

Yak Posting Veteran

67 Posts

Posted - 07/27/2001 :  12:43:22  Show Profile  Reply with Quote
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?

Go to Top of Page

Yak Posting Veteran

67 Posts

Posted - 07/31/2001 :  11:13:31  Show Profile  Reply with Quote
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?

Go to Top of Page
  Previous Topic Topic Next Topic  
 Reply to Topic
 Printer Friendly
Jump To:
SQL Server Forums © 2000-2009 SQLTeam Publishing, LLC Go To Top Of Page
This page was generated in 0.02 seconds. Powered By: Snitz Forums 2000