Re: Breaking into a running app?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Ed (Ed_Millis_at_NOSPAM.yahoo.com)
Date: 08/25/04 

Date: Wed, 25 Aug 2004 09:27:49 -0700

Great idea, Robert! In fact, I've got some class modules that I used in an
Excel VBA routine that basically did just that. Should be easy enough to
add to the app; then, if a user reports problems, I can go back and look at
the report and see what happened where.

I appreciate the boost.
Ed

"Robert Suffecool" <rmsuffy@hotmail.com> wrote in message
news:uKbvKmriEHA.3476@tk2msftngp13.phx.gbl...
> I agree with Veign... creating a installation package may solve your
> problems. However, if you wanted to debug your compiled app in real time
> then you could create a class that reports the application status to a
> database... in affect, timestamping what is going on in the app while
> running the compiled verison. After reviewing the records in the
database,
> you could easily to back and look at the code when you find something in
the
> database that concerns you.
>
> The best way to create this class, I think, is a combination of error
> handling and in regular code. For example, whenever a procedure runs, you
> could add an entry into the database timestamping when it ran along with
any
> information you would like to know -- i.e., maybe you'd like to know what
> variable x equaled when the procedure ran, etc...etc...
>
> Anyway... just an idea...
>
> Robert
>
>
> "Veign" <NOSPAMinveign@veign.com> wrote in message
> news:uVddcFriEHA.1184@TK2MSFTNGP12.phx.gbl...
> > You don't mention what problems you are having with the application on
the
> > server. Also, why don't you create an installation package and
'install'
> it
> > on the server - this may clear up your problems.
> >
> > --
> > Chris Hanscom
> > MVP (Visual Basic)
> > http://www.veign.com
> > --
> >
> > "Ed" <Ed_Millis@NOSPAM.yahoo.com> wrote in message
> > news:eRrLQ5qiEHA.2848@TK2MSFTNGP10.phx.gbl...
> > > When I test my app on my computer with my test files, everything is
> great.
> > > When I put this thing on the network and run it from there, I get some
> > > glitches. I "publish" this app and the associated files to a server
> just
> > by
> > > copying over the whole complete folder; I compile and make an exe, but
> > don't
> > > "package" the app.
> > >
> > > Is there a way I can "break" into the app when I run it to step
through
> a
> > > spot that's giving me problems? Or a "maintenance mode" I can build
> into
> > it
> > > that will let me access a "step-though" mode for troubleshooting this
> > thing
> > > in its real-world-use environment?
> > >
> > > Ed
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: SYSTEMS ENGINEER/ VAX-VMS/ CAREER POSITION
    ... System Administration and database admin from NIIT, ... salary details and generate reports and enclosures,and calculates ... Responsibilities: ... Write New programs from user requirements, Programming Changes ...
    (comp.os.vms)
  • Re: Selling the boss on a "publish to the web" Access app?
    ... provide a link to the database to users and they could come in to the site, run reports, etc. ... Can you find me an example of a database online and don't have to login that was written in asp.net for example? ... You REALLY need to adopt some overall secure model for your web systems, regardless of what your goal is here. ... So the idea of a one click to publish to some system, certainly means that you're going to have to adopt a web server with a FIXED set of standards. ...
    (comp.databases.ms-access)
  • Re: Advice needed for a growing Access 2000 project
    ... However, it turned out that quite a few of those were "leftovers" from previous releases, no longer accessible from anywhere but the database window, and, thus, no longer used. ... But that certainly isn't the _norm_ -- without any 'heroic' measures, there are routine reports of split Access DBs ... Finally, in my opinion, for "Windows apps", that is, individual-user applications, modest-sized multiuser applications, and client-server applications of any size, Dot Net does NOT "help along" any of these issues. ... The post I reference was in reference its self to the MS Access Help file under "Microsoft Access database general specifications" ...
    (comp.databases.ms-access)
  • Re: running report cause fatal error- on Win98, not XP
    ... It is actually not that difficult to crash JET with complex queries, ... another query. ... only the more complex reports cause the crash- the others do ... Then compact the database: ...
    (microsoft.public.access.reports)
  • Re: running report cause fatal error- on Win98, not XP
    ... another query. ... only the more complex reports cause the crash- the others do ... Then compact the database: ... Still in the code window, choose Compile from the Debug menu. ...
    (microsoft.public.access.reports)