Link to home
Start Free TrialLog in
Avatar of deepu712
deepu712

asked on

Vb Tool

1) Can Someone please let me know how to convert word document into power point and vice versa using vb6.
2) Any idea how to make a vb tool to get the trace of your vb exe and related dll(like sql trace).it sould give the  trace of flow and tell clearly where application is failing(dll or exe).I have been ask to write such tool for one of my application as it keeps on failing and we always break our head to find out where its failing...
ASKER CERTIFIED SOLUTION
Avatar of DominicCronin
DominicCronin
Flag of Netherlands image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of deepu712
deepu712

ASKER

Hi Domi,
         
             Appreciat your reply.
  First Question:
          I already tried this option, the main problem i am facing in copying from word to power point is
           how and when to insert a new power point slides(new page).
  Second Quesion:
          Dll has not been created by me and sadly my manager doesn't want me to write same dll
         (we dont have source)again,instead of that he wants me to find out some tools to track out the flow of
        the programe.
Recording a quick powerpoint macro gives:

ActiveWindow.View.GotoSlide Index:=ActivePresentation.Slides.Add(Index:=2, Layout:=ppLayoutText).SlideIndex

You might have to fiddle with it a bit, but that's how it's done. (You can probably miss out the GotoSlide part)

As for "when", that's trickier. If the Word documents are already laid out as slides, with suitable outlining and styles, then it should be reasonably straightforward. Otherwise, you'll have to come up with an algorithm based on the size of text etc. I'm actually having trouble trying to imagine what sort of documents you have to work with here. There aren't many kinds of word documents that it would make sense to convert to powerpoint.

As for the tracing issue. Firstly, what's the point? If you haven't got the source, what will you do if you *do* manage to find out where it's broken? Frankly, I would have to say that the best way to solve your problem is to educate your boss. There are very few options if you don't have the sources. Perhaps if there's an unhandled exception, you might be able to attach a debugger when it breaks, but that won't tell you much, except where in the dll or exe it's breaking.

Presumably if you haven't got the source, it's a dll made by someone else. The only people who can meaningfully do anything for you are the people who made it, and therefore have the source.