Re: QRe: Legacy Access 2 VB 4 app, Word 11 merge on XP Pro SP2 client
From: John Nurick (j.mapSoN.nurick_at_dial.pipex.com)
Date: 01/29/05
- Next message: ITJRW: "Re: QRe: Legacy Access 2 VB 4 app, Word 11 merge on XP Pro SP2 client"
- Previous message: ITJRW: "QRe: Legacy Access 2 VB 4 app, Word 11 merge on XP Pro SP2 client"
- In reply to: ITJRW: "QRe: Legacy Access 2 VB 4 app, Word 11 merge on XP Pro SP2 client"
- Next in thread: ITJRW: "Re: QRe: Legacy Access 2 VB 4 app, Word 11 merge on XP Pro SP2 client"
- Reply: ITJRW: "Re: QRe: Legacy Access 2 VB 4 app, Word 11 merge on XP Pro SP2 client"
- Reply: david epsom dot com dot au: "Re: QRe: Legacy Access 2 VB 4 app, Word 11 merge on XP Pro SP2 client"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 29 Jan 2005 21:21:03 +0000
On Sat, 29 Jan 2005 14:47:52 -0600, "ITJRW" <justice@community.nospam>
wrote:
>Indeed. I find it a challenge. I would simply write a short interim app as
>a temporary merge from DSN-less SQLConnect() (which I've been able to
>successfully connect to the .mdb files and access the tables) into a cursor
>containing only the data desired. However the data is collected from
>several tables via over 24 records of steps in a "Logic" table. I suspect
>it may be placing them into a cursor long enough to create the .dat file but
>don't know for sure. I just know that it uses three of these logic record
>sets to retrieve the data. I would suspect that I may not have any
>restriction on doing this if I make the cursor read-only with Sequal Pass
>Trough approach. I guess I could locate the data in the original records of
>the various tables and create a SQL statement to retrieve all of these
>values and add my own he/she his/her values based on a "Sex" field value.
I'd think of it in terms of creating an Access 2003 database and using
linked tables to connect to the data in the legacy .mdb files. But it's
largely a question of the tools one's used to.
>Bottom line here is that I am developing a replacement application with new
>interfaces and tables and will ultimately bring these records into my own
>structures since the lady who developed the app is unwilling to update it
>and the client has asked me to develop a new app with more features anyway.
>I've been working on it alone since last August. It's mighty robust.
<snip>
>Where would I look for the runtime and what is it called? I assume it is a
>dll. Since I have Access 11 and the Access 2 converter on my development
>machine, do you believe I could identify it with certainty without going to
>the next county about an hour away for me?
No, it's not a DLL but essentially the whole of Access 2.0 with the
design-mode capabilities disabled. Search your workstation's HD for
msaccess.exe. If you find one that's the wrong age and the wrong
location for your Office 2003 installation, with other Access files in
the same folder, that's probably it.
<snip>
>> I don't understand what you mean by
>> <sometimes-short-merge-document-filename>.dat
>
>I mean that if the name of the merge document is longer than the old 8.3
>standard the .dat file is given the short file name. Examples:
>"Indictment.doc" named merge document will cause the app to create
>"Indict~1.dat" and "Motrev.doc" named merge document will cause the app to
>create "Motrev.doc" I hope that is a bit clearer.
That makes sense.
<snip>
>The application is performing exactly as it did on Windows 98 machines and
>NT 4.0 server in all respects except the merge doesn't even open MS Word 11,
>much less merge. The application used to open Word with the merge document
>merged into a new document with the data source (.dat file) providing the
>data for the merge fields. When they upgraded to OS XP Pro and Office 2003
>Standard the merge was "broken." Therefore, you must be right.
<snip>
>I researched the install.log of the application and found many "errors" such
>as the following.
>The following files were not installed:
>C:\Windows\Systeme32\Vb5db.dll
>------same path-------- \Stdole.dll
>------same path-------- \Stdole2.tlb
>------same path-------- \P2sodbc.dll
>------same path-------- \Olepro32.dll
>------same path-------- \Oleaut32.dll
>------same path-------- \Odbctl32.dll
>------same path-------- \Odbcjt32.dll
>------same path-------- \Odbcji32.dll
>------same path-------- \Odbc32.dll
>------same path-------- \Ms*.dll including jet35, and Msvbvm50
>Also Mfc42.dll and Mfc40.dll and many ODBC*.dll, .exe .cpl, .cnt.
>
>Most of the above I've checked and they were'nt installed due to newer
>versions being on the machine.
>
>In addition the install would not self register the following:
>vbajet32.dll, vb5db.dll, stdole2.tlb, p2sodbc.dll, several ODBC??32.dlls,
>msjter35.dll and msjter35.dll most of these because they could not be copied
>to the <system>\System32\folder. I have administrator rights and so did the
>users when the application was installed on their machines (now they don't
>since I installed a W2K3 server and improved security matters).
>
>I believe this problem is a typical "dll hell" problem from what I'm seeing.
>
>I don't know if this would give you any insights into what the application
>is using since there are dlls for ODBC, OLE, and Jet.
This is emphatically not an area I understand. Could it be that the
files couldn't be copied because they already existed? The one thing is
that for DDE and OLE the application wouldn't normally need the name and
location of winword.exe.
-- John Nurick [Microsoft Access MVP] Please respond in the newgroup and not by email.
- Next message: ITJRW: "Re: QRe: Legacy Access 2 VB 4 app, Word 11 merge on XP Pro SP2 client"
- Previous message: ITJRW: "QRe: Legacy Access 2 VB 4 app, Word 11 merge on XP Pro SP2 client"
- In reply to: ITJRW: "QRe: Legacy Access 2 VB 4 app, Word 11 merge on XP Pro SP2 client"
- Next in thread: ITJRW: "Re: QRe: Legacy Access 2 VB 4 app, Word 11 merge on XP Pro SP2 client"
- Reply: ITJRW: "Re: QRe: Legacy Access 2 VB 4 app, Word 11 merge on XP Pro SP2 client"
- Reply: david epsom dot com dot au: "Re: QRe: Legacy Access 2 VB 4 app, Word 11 merge on XP Pro SP2 client"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|