A client has a customer that wants the output from my client’s programs to
be in “Access Table format” so he can use it directly in his W*****'s
applications.
Does anyone know if the specifications for Access files have ever been
published by Mr Gates & Co or anyone else. And, if there are any C library
packages for QNX 4 (Watcom 10.6) to make this project less painfull?
Bob Harris In short, you may buy a servant or slave,
Bath, NH but you cannot buy a friend.
bob@microprograms.com (Thoreau: Wild Fruits)
Bob
Would it be unacceptable to your client to use CSV files or similar.
Access can then import them. Alternatively you could do ODBC to your
applications data files.
If security is an issue then perhaps you could use PostgreSQL and link
access to it.
I don’t think you would gain any advantage by creating Access Tables
formats over straight CSV.
Paul
In article <97rhur$8fm$1@inn.qnx.com>, bob@microprograms.com (Robert L.
Harris) wrote:
A client has a customer that wants the output from my client’s programs
to
be in “Access Table format” so he can use it directly in his W*****'s
applications.
Does anyone know if the specifications for Access files have ever been
published by Mr Gates & Co or anyone else. And, if there are any C
library
packages for QNX 4 (Watcom 10.6) to make this project less painfull?
Bob Harris In short, you may buy a servant or slave,
Bath, NH but you cannot buy a friend.
bob@microprograms.com > (Thoreau: Wild Fruits)
CSV (comma separated variables) would be my vote too. In the past when I have
had similar requirements you usually find two things:
- The Windows file format is not officially documented and so you rely on
third-party hacks of the information
- The file formats change as versions change, and so working code could
well be broken by a version upgrade on the Win side.
Save yourself the grief and go with something you can see inside. If you
ignore that, I have had good success (subject to the above warning) at
www.wotsit.org
But they were offline when I just checked.
Paul McCormack wrote:
Bob
Would it be unacceptable to your client to use CSV files or similar.
Access can then import them. Alternatively you could do ODBC to your
applications data files.
If security is an issue then perhaps you could use PostgreSQL and link
access to it.
I don’t think you would gain any advantage by creating Access Tables
formats over straight CSV.
Paul
In article <97rhur$8fm$> 1@inn.qnx.com> >, > bob@microprograms.com > (Robert L.
Harris) wrote:
A client has a customer that wants the output from my client’s programs
to
be in “Access Table format” so he can use it directly in his W*****'s
applications.
Does anyone know if the specifications for Access files have ever been
published by Mr Gates & Co or anyone else. And, if there are any C
library
packages for QNX 4 (Watcom 10.6) to make this project less painfull?
Bob Harris In short, you may buy a servant or slave,
Bath, NH but you cannot buy a friend.
bob@microprograms.com > (Thoreau: Wild Fruits)
Thanks, guys.
That is what I would prefer to do (and did earlier for another of my
client’s customers). Because the new customer is being a little pushy, I
said I’d make queries to see if the situation had changed.
Unfortunately, some people have been so blind-sided by MS that they can’t
see beyond their noses. In those cases, one has to do a major justification
of one’s proposals.
Bob
“Donald Backstrom” <donaldb@cstgroup.com.au> wrote in message
news:3AA2CEAA.66C3A14A@cstgroup.com.au…
CSV (comma separated variables) would be my vote too. In the past when I
have
had similar requirements you usually find two things:
- The Windows file format is not officially documented and so you rely
on
third-party hacks of the information
- The file formats change as versions change, and so working code
could
well be broken by a version upgrade on the Win side.
Save yourself the grief and go with something you can see inside. If you
ignore that, I have had good success (subject to the above warning) at
www.wotsit.org
But they were offline when I just checked.
Paul McCormack wrote:
Bob
Would it be unacceptable to your client to use CSV files or similar.
Access can then import them. Alternatively you could do ODBC to your
applications data files.
If security is an issue then perhaps you could use PostgreSQL and link
access to it.
I don’t think you would gain any advantage by creating Access Tables
formats over straight CSV.
Paul
In article <97rhur$8fm$> 1@inn.qnx.com> >, > bob@microprograms.com > (Robert L.
Harris) wrote:
A client has a customer that wants the output from my client’s
programs
to
be in “Access Table format” so he can use it directly in his W*****'s
applications.
Does anyone know if the specifications for Access files have ever been
published by Mr Gates & Co or anyone else. And, if there are any C
library
packages for QNX 4 (Watcom 10.6) to make this project less painfull?
\
Bob Harris In short, you may buy a servant or
slave,
Bath, NH but you cannot buy a
friend.
bob@microprograms.com > (Thoreau: Wild
Fruits)
\