Search results for query: *

Since my original posting, I've tried using late binding (changing both WordApp and WordDoc to type Object), using a local Word document that I just created (and clearly have rights to) which has no spaces in the file spec, Word.Application.12 instead of Word.Application (that won't compile)...

Earlier this year, I developed a VB 6 application to automatically generate letters as Microsoft Word documents. After extensive testing and debugging, it worked flawlessly on my Win XP development machine. Now, while I'm attempting to troubleshoot a run-time error the end users are having...

I have tried using SharePoint designer, but when I open either of those pages in it all I see are three generic labels and three generic text boxes (Column Name 1, Column Value 1, Column Name 2, etc.) with no indication of how any of them relates to the dozen or so fields in my list. The code...

In SharePoint 2007, I am implementing a support ticket tracking system. I need to be able to customize the alert email messages that are sent. Specifically, I need to have those messages either (a) contain the complete text of the record that generated the alert; or (b) contain a direct link...

In SharePoint 2007, I am implementing a support ticket tracking system. I know how to modify the default view so that the autonumber/identity field (Issue ID) appears in that view, but it still does not appear when viewing or editing an individual record. Management could live with the number...

This turned out to be a permissions issue. After granting all users the right to read and execute the .OCX file on the local machine, the problem disappeared.

I develop and maintain several VB6 applications used internally by my employer. All PCs (both my development machine and the users' workstations) run Windows XP. My normal procedure is to develop and test the application, and build an installation package (using the Package and Deployment...

Those modifications require accessing and modifying code, which I don't know how to do in SharePoint. The alternative I came up with was to use folders within a single library to organize documents, and management has approved that choice.

I can remove the unwanted fields from all views, and those changes are reflected when the library is viewed on its own page. But for some reason, when it's viewed in the page where it's been inserted as another web part, the unwanted fields return and there is no "View" drop-down list to...

On a new site, I need to set up a document library divided into sections, with a label at the top of each section. The only way I've found to make this happen is to set up two regular document libraries, display the first one, choose Edit Page from the Site Actions drop-down, click the Add a...