I'm not sure what you mean....
It passes CanCheckOut before CheckOut
I am not trying CanCheckIn before CheckIn since my script is responsible for having checked the document out beforehand.
Hello All,
I'm trying to run a macro that was written in Excel 2007 on a computer that is running Excel 2003.
Set wb = Workbooks.Open(path)
wb.Save
wb.Saved = True
wb.CheckIn <--- Err: Appilcation-defined or object-defined error
This code works perfectly using Excel 2007.
I've tried...
well, the directory i'm working with is actually a SharePoint document library. using SP you can define custom properties. you can use contenttypeproperties to read those custom properties from the files.
the problem is, i don't know of a way to read the properties without first knowing the...
hello all,
i'm new to all of this, so please forgive me if i'm not making sense...
i'm writing an excel 2007 vba macro that should traverse a directory and get the contenttypeproperties of each file.
the directory will contain many different document types - doc, xls, pdf to name a few.
the...
the query works just fine from a sproc. so, i've created a sproc that truncs then pops a table. the asp page now execs the sproc then selects from the table.
it's just a temporary workaround until we better organize our data. it's not terribly quick, but that nasty UNION table took forever to...
wow...
so, the second select statement returned 0 records. just for kicks, i commented it out - leaving the remaining 5 select statements (all of which have a result set) uncommented. the stinkin thing works now.
anybody ever hear of anything like that???!!!
it's gotta be a fluke. testing...
hello all... having trouble with a query. possibly too many UNIONs? - eats too much memory? - i don't know...
the error produced:
DATE/TIME: 4/30/2009 10:27:15 AM
DESCRIPTION: Error: 0, Severity: 19, State: 0
SqlDumpExceptionHandler: Process 67 generated fatal exception c0000005...
A better example: (from http://devpinoy.org/blogs/bonskijr/archive/2006/02/16/1708.aspx)
An interesting application
I have used stored procs extensibly in my application, but I was kind of frustrated when a situation arises that not all parameters will be used for either an INSERT or UPDATE...
Found the following example of default sproc values at http://www.daveandal.net/books/6744/dataaccess/sprocdefaults.aspx
Is this the right idea - or are there improved/advanced ways yet?
---------------
Using Default Values in a Stored Procedure
Executing the SQL Server stored procedure...
>>> And seriously... 15 columns isn't all that much.
You're right - I under-exaggerated... it's actually over 50. I suppose the best way to do this is to only use the fields I need as I go... meaning, of the 50 fields, I'm really only updating/inserting 15 or so for the majority of the time...
OK - That's a step in the right direction. Thanks. But I'm thinking that having to call an update sproc that expects 15+ params is a problem. In other words, why call thisSproc(f1,f2,f3,f4,f5,f6,f7,...,fx) if I only want to update one field? So maybe the answer is to create a sproc that only...
Hello All,
I have a question regarding SQL industry best practices. Specifically calling stored procedures from server side scripting (in this case C#). My current sproc and C# pseudo-coded below - question to follow.
SQL:
create putData
{
@recID
@actionFlag
@field1
@field2
@field3
...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.