Re: Commercial release Newbie
From: John Nurick (j.mapSoN.nurick_at_dial.pipex.com)
Date: 10/14/04
- Next message: Jamie Collins: "Re: Question for Joe Fallon--determining Data type"
- Previous message: david epsom dot com dot au: "Re: msexch35.dll"
- In reply to: Karen: "Commercial release Newbie"
- Next in thread: Karen: "Re: Commercial release Newbie"
- Reply: Karen: "Re: Commercial release Newbie"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 14 Oct 2004 06:49:09 +0100
Hi Karen,
Like Alex's, my first assumption would be that there was a bug in my
code, perhaps relating to subtle differences between Word 2002 and 2003
(which alas do exist).
What versions of Access are involved on the various machines? Which
version did you use to create the mde front end? Are you using early or
late binding to automate Word?
For troubleshooting, I'd install an mdb version of the front end on the
"different" machine (or if distance to the client's colleague prohibits
this, set up a computer for myself with the same OS and Office app
versions and service packs). It's then possible to step through the code
and find out exactly the circumstances in which the error message is
being generated.
Alternatively create a "debugging" version of the mde, with code in the
suspect procedure(s) that double-checks everything and writes a detailed
log file that you can examine back home.
On Wed, 13 Oct 2004 13:21:40 -0600, "Karen" <wonderlover@functiy.com>
wrote:
>If my following question is better asked in another group, feel free to
>point me to the applicable group.
>
>As background, I've been working for the past two years developing custom
>Access apps for small businesses. Because the app was custom designed and
>developed for individual customers it was easy to accommodate the customer's
>particular computer/software configurations.
>
>One customer, however, was very pleased with his app and felt it could be
>distributed to others in his particular line of work. He has funded the
>further development necessary to make the app a 'product'. We have been
>distributing the app to a few of his colleagues in a 'Beta' sense and have
>added some features as a result of the feedback we've received.
>
>In the application, several different reports are available to the user.
>These reports open Word. My VBA code opens Word, creates a document based
>on a Word template, unprotects the Word document to push info from the
>database then protects the document so only certain sections can be edited
>by the user.
>
>The Beta installations have all been on systems with XP Pro and Word 2003.
>Yesterday, we installed the app on a system running XP Home and Word 2002.
>When a report is attempted, Access throws an error message that the Word
>document cannot be 'unprotected' as it already is 'unprotected'.
>
>My question is 'Could this be because we're using XP Home vice XP Pro or
>because we're using Word 2002 vice Word 2003?
>
>As a newbie to developing a commercial release, any suggestions for how I
>might find some resource to help me through these sort of global issues?
>
>I know this is a lot but I really want to build a useful app and my
>experience level is clearly not up to this last stretch.
-- John Nurick [Microsoft Access MVP] Please respond in the newgroup and not by email.
- Next message: Jamie Collins: "Re: Question for Joe Fallon--determining Data type"
- Previous message: david epsom dot com dot au: "Re: msexch35.dll"
- In reply to: Karen: "Commercial release Newbie"
- Next in thread: Karen: "Re: Commercial release Newbie"
- Reply: Karen: "Re: Commercial release Newbie"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
