tranchemontaigne
Registered User.
- Local time
- Yesterday, 19:34
- Joined
- Aug 12, 2008
- Messages
- 203
Recently I ran into a problem where I used the "Microsoft Scriptlet Library" to create external files and write content to them as part of an HL7 messaging integration. The problem with this approach is that the default encoding used when writing strings to these files was UTF-8 (a two bit character encoding scheme), when the consuming system required a single bit character encoding scheme such as Windows-1252 or ASCII.
I worked through the problem by using "Microsoft ActiveX Data Objects 2.8 Library" and the ADODB.Stream object to create files and write content to them because it accepts an encoding scheme parameter.
Fortunately, all my code used ADODB recordsets, so calling a previously referenced library for something else was trivial. Given the apparent preference for DAO among MS Access developers, I was curious to learn how a developer who prefers DAO would have solved this problem.
I worked through the problem by using "Microsoft ActiveX Data Objects 2.8 Library" and the ADODB.Stream object to create files and write content to them because it accepts an encoding scheme parameter.
Fortunately, all my code used ADODB recordsets, so calling a previously referenced library for something else was trivial. Given the apparent preference for DAO among MS Access developers, I was curious to learn how a developer who prefers DAO would have solved this problem.