This isn't going to make me sleep any better, but thanks for the
information. Unfortunatley, this also doesn't resolve either of our
situations.
The one thing in my favor, is that I haven't gone live yet with 4.0 and
everything works just fine with 3.0. The push is on to go to 4.0 because the
President also wants us on APS scheduling. Anybody using APS with Morocco?
Any problems I should be aware of? Any suggestions as to how
we might resolve this Access issue, would also be appreciated.
Thanks,
Les
I am in the exact situation regarding an Access Estimating system. All I
can tell you is that the 3.6 driver with Access 2000 still gives the error.
I understand that Access 2000 does not use the Jet engine, but that hasn't
solved the problem for us. Also, if the number of characters in certain
fields were the issue, I would think that the problem would be more
consistent. In my experience, it may occur or not occur on the same set of
data at any given time.
-----Original Message-----
From: Les Tingley [mailto:
ltingley@...]
Sent: Thursday, August 17, 2000 11:20 AM
To: '
vantage@egroups.com'
Subject: RE: [Vantage] 3146 ODBC call failed
No option here. We are primarily a custom Job shop and have invested 2 years
and many thousands of dollars to develop this Access Estimating package. To
make matters worse, we needed Custom Programming to develop a Quote Importer
module to pull the data into vantage. This had to be done again at an
additional cost to upgrade to 4.0. If it were up to me, we'd be using the
stock Vantage Quote Module. All to often, the estimate is based on what the
market dictates anyway. The Custom Estimating program is our company
presidents pet project. Need I say more? Tech support suggest the issue is
due to the number of characters in certain fields. They further suggest that
the 3.6 driver does not double this number when it grabs them from Progress.
Access 2000 does not use the Jet engine. Have you discovered this not to be
true, or are there other issues we should know about? This sounds like
another issue where the resolution is not so cut and dry. "I could have been
a Dentist!"
Les
Les,
I have the Merant driver 3.6, and I am running it with Access 2000. I
wouldn't recommend spending any money on either if the reason for doing so
is to fix this problem.
B
-----Original Message-----
From: Les Tingley [mailto:
ltingley@...]
Sent: Thursday, August 17, 2000 9:50 AM
To: '
vantage@egroups.com'
Subject: RE: [Vantage] 3146 ODBC call failed
I just had a similar issue testing our Access 97 Estimating package with
Merant Driver 3.5 Sql 9.2 Tech support gave me a couple of options. Migrate
to Access 2000 or obtain Merant Driver 3.6. I have requested 3.6. Apparently
part of the issue is the limitations of the Access Jet Engine regarding the
number of characters it can handle in an indexed field. Merant driver 3.5
doubles the number of characters when it grabs them from the Progress
database. Merant driver 3.6 does not do this. They gave a third option of
changing the number of characters exported to ODBC within the data
dictionary (changing the character format). Between Access and the Merant
3.5 driver, there may be a problem linking to a field with more than 24
characters. Tech support recommends contacting them for further information
regarding this last option. Sounds shaky at best.
Les
This subject has come up before:
On 7/31/00, John Yohannan wrote
"I'm getting an error when trying to update links in an Access97 database
using the Merant driver. I get the error -- 3146 ODBC call failed --"
Since there has been no response to this message, I have to assume that no
one has a good answer. Previously, there were several emails beginning with
H. Dale Puls, who had the same problem. This string eventually went off on
a tangent about how to get Vantage to talk to UPS. There were no
suggestions about possible solutions to the ODBC problem.
At any rate, I just wanted to keep this thing alive, incase someone comes up
with a solution. If you do, please don't forget to post it for the rest of
us.
Thanks...B
We no longer allow attachments to files. To access/share Report Files,
please go to the following link:
http://www.egroups.com/files/vantage/
(Note: If this link does not work for you the first time you try it, go to
www.egroups.com, login and be sure to save your password, choose My Groups,
choose Vantage, then choose Files. If you save the password, the link above
will work the next time you try it.)
We no longer allow attachments to files. To access/share Report Files,
please go to the following link:
http://www.egroups.com/files/vantage/
(Note: If this link does not work for you the first time you try it, go to
www.egroups.com, login and be sure to save your password, choose My Groups,
choose Vantage, then choose Files. If you save the password, the link above
will work the next time you try it.)
We no longer allow attachments to files. To access/share Report Files,
please go to the following link:
http://www.egroups.com/files/vantage/
(Note: If this link does not work for you the first time you try it, go to
www.egroups.com, login and be sure to save your password, choose My Groups,
choose Vantage, then choose Files. If you save the password, the link above
will work the next time you try it.)
We no longer allow attachments to files. To access/share Report Files,
please go to the following link:
http://www.egroups.com/files/vantage/
(Note: If this link does not work for you the first time you try it, go to
www.egroups.com, login and be sure to save your password, choose My Groups,
choose Vantage, then choose Files. If you save the password, the link above
will work the next time you try it.)
We no longer allow attachments to files. To access/share Report Files,
please go to the following link:
http://www.egroups.com/files/vantage/
(Note: If this link does not work for you the first time you try it, go to
www.egroups.com, login and be sure to save your password, choose My Groups,
choose Vantage, then choose Files. If you save the password, the link above
will work the next time you try it.)