Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations GregLocock on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

DSOFILE X configuration specific properties

Status
Not open for further replies.

macPT

Mechanical
Oct 22, 2002
607
With DSOFILE I am able to read and modify properties of documents, including SW doc., without the need to open the files, but I can only access summary properties and the "normal" custom properties. Does anyone knows how to read and write configuration specific properties with DSOFILE? Is it possible?

Thanks
 
Replies continue below

Recommended for you

I don't think you can with DSOFile. I use DSOFile religiously to push/pull Custom Properties. I have done what you ask using SW-API whilst the file is open, but don't remember if I was ever successfull with DSOFile. I'll check today.

And, since I am having a weird DSOFile problem, are you using your DSOFile stuff on an XP machine? If so, I need to talk to you about it.

Mr. Pickles
 
I use DSOFILE on W2K and without any problem so far. I have a small VBA program, which can run for SW or for any other MS docs., and there is no need to have the files opened to access the properties. I have another Excel-VBA program to manage the properties (custom and configuration specific)in SW docs., that do the job with active doc. Thats the standard procedure when we are designing products. But, for checking properties or for modify a property in a group of files, DSOFILE is the way to go. The problem is that I don't know how to access the configuration specific properties (I suppose that this is specific to SW and MS didn't predicted to use DSOFILE in this way).

Thanks
 
I hear and agree with you. My problem with DSOFile is that on Win2K all is fine with my Excel VBA file. When I tried it on a Win XP system, the Excel file will NOT load. Excel crashes upon opening and want's to send a report to M$.

If you know someone with XP, ask them to try it. They will need DSOFile registered (regsvr32). Interesting to see if it works for them....

Mr. Pickles
 
I never heard about problems in XP (the reason could be the fact that I don't know to much people working with SW on XP). Are you using the "real" DSOFILE, dowloaded from MS site? In my first atempt to use DSOFILE, I used a file downloded from a site related to SW macros and tips, and it was not working properly.
 
Yeah, I have tried 3 different versions. Oddly, at the M$ site, you can find a link to download it, it says it is version 1.3, but when you look in your registry or properties of the file, it claims to be 1.4.

I have tried the install routine that comes with some versions, and have manually registered it using regsrv32.

I'm not sure, but I think that DSOfile was supposed to be a "stop gap" to use since VB6 couldn't swap Custom Property info without some possible problems since the 2 "routines" in VB for it weren't neccessarily automation compliant.

So my theory is that the DSOfile is not compatible with XP and that VB.Net has the DSOfile functionality built-in. Therefore M$ isn't too keen on making a new one, since they would prefer to sell numerous copies of what I think is overpriced ".Net" stuff.

But, maybe it is just my computer. If DSOfile is on there, it crashes, if not it doesn't...

Mr. Pickles
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor