Good afternoon,
I'm from Venezuela. I'm currently working with D3 version 7.50, which is over 20 years old due to the well-known economic crisis. My name is Rafael Rivas and I'm from Venezuela. I'm currently working with D3 version 7.50, which is over 20 years old due to the well-known economic situation in my country and the lack of resources to update it to the latest version.
I'm having ODBC compatibility issues when trying to connect Microsoft Access to my D3 database. Due to these issues, I'm unable to establish a proper connection.
If anyone could help me, I would greatly appreciate it. I specifically need the ODBC64 version to resolve this issue.
Thank you in advance for any help.
Best regards,
Rafael Rivas
------------------------------
Rafael Rivas
Rafael Rivas
Self Registered
La guaira VE
------------------------------
Hello Rafael,
If I understand your post correctly; a summary could be:
- Old version of d3 [7.5]
- New version[s] of Microsoft Access and
- [Possibly] new versions of Windows itself.
This combination no longer wants to talk to d3 v7.5 due to ODBC compatibility.
Is it fair to say Microsoft is earning $ from you or your customer for their new products, but Rocket is not? Or are you replying on free versions?
If I am off-base here or completely misunderstood; I apologise as my intent is to help. I understand commercial and economic realities can be very painful.
If that is accurate, then the only way you can solve this is to ask Rocket if you may have a copy of the necessary updated components [ODBC64] free. Of course, that will only help if that component will 'behave' on v7.5. Frankly I doubt it; but it may?
I recommend you open a ticket with Rocket support as Brian Cram and others can probably explain your options far better than I at this point.
Best wishes,
------------------------------
David Knight
Senior Software Engineer
H3O Business Technologies Limited
------------------------------
Hello Rafael,
If I understand your post correctly; a summary could be:
- Old version of d3 [7.5]
- New version[s] of Microsoft Access and
- [Possibly] new versions of Windows itself.
This combination no longer wants to talk to d3 v7.5 due to ODBC compatibility.
Is it fair to say Microsoft is earning $ from you or your customer for their new products, but Rocket is not? Or are you replying on free versions?
If I am off-base here or completely misunderstood; I apologise as my intent is to help. I understand commercial and economic realities can be very painful.
If that is accurate, then the only way you can solve this is to ask Rocket if you may have a copy of the necessary updated components [ODBC64] free. Of course, that will only help if that component will 'behave' on v7.5. Frankly I doubt it; but it may?
I recommend you open a ticket with Rocket support as Brian Cram and others can probably explain your options far better than I at this point.
Best wishes,
------------------------------
David Knight
Senior Software Engineer
H3O Business Technologies Limited
------------------------------
Dear Mr. David Knight,
Thank you for responding to my concern. You are absolutely right in what you kindly mentioned about Microsoft—they are the ones who take the profits, and rightfully so, for their work in developing new versions. Unfortunately, in our country, things have changed significantly. Many companies that once acquired the D3 system have been forced to shut down, leaving only a few that have managed to survive with great effort.
As a result, we, the programmers who are passionate about D3, have struggled to keep these companies running, often working with limited resources. However, we have now reached a breaking point. The latest government regulation states that software must comply with certain standards, including the ability to access the D3 database for billing purposes. If we are unable to meet this requirement, we will no longer be able to continue working.
For this reason, we are urgently searching for the 64-bit ODBC driver to see if we can comply with this regulation. If we fail, we will have no choice but to say goodbye to our jobs. In my case, I have been working with D3 since 1984, and this could mark the end of D3 in Venezuela.
Best regards,
Rafael Rivas
------------------------------
Rafael Rivas
Rafael Rivas
Self Registered
La guaira VE
------------------------------
Hello Rafael,
If I understand your post correctly; a summary could be:
- Old version of d3 [7.5]
- New version[s] of Microsoft Access and
- [Possibly] new versions of Windows itself.
This combination no longer wants to talk to d3 v7.5 due to ODBC compatibility.
Is it fair to say Microsoft is earning $ from you or your customer for their new products, but Rocket is not? Or are you replying on free versions?
If I am off-base here or completely misunderstood; I apologise as my intent is to help. I understand commercial and economic realities can be very painful.
If that is accurate, then the only way you can solve this is to ask Rocket if you may have a copy of the necessary updated components [ODBC64] free. Of course, that will only help if that component will 'behave' on v7.5. Frankly I doubt it; but it may?
I recommend you open a ticket with Rocket support as Brian Cram and others can probably explain your options far better than I at this point.
Best wishes,
------------------------------
David Knight
Senior Software Engineer
H3O Business Technologies Limited
------------------------------
Use MS Query instead of Access's ODBC connection. The problem is that Access's ODBC connection uses version 3.x where MS Query uses 2.5 or something like that. D3's ODBC connector does not support 3.x, even in the newest versions.
------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------
Use MS Query instead of Access's ODBC connection. The problem is that Access's ODBC connection uses version 3.x where MS Query uses 2.5 or something like that. D3's ODBC connector does not support 3.x, even in the newest versions.
------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------
Thank you, Mr. Brian Cram, for your response and for taking the time to reply to me. If it’s not too much trouble, could you provide an example? I am not very familiar with MS Query. That is, of course, if your valuable time allows it.
Rafael Rivas
Analista Programador
------------------------------
Rafael Rivas
Rafael Rivas
Self Registered
La guaira VE
------------------------------
Thank you, Mr. Brian Cram, for your response and for taking the time to reply to me. If it’s not too much trouble, could you provide an example? I am not very familiar with MS Query. That is, of course, if your valuable time allows it.
Rafael Rivas
Analista Programador
------------------------------
Rafael Rivas
Rafael Rivas
Self Registered
La guaira VE
------------------------------
Working on it...
------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------
Working on it...
------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------
From Excel, data tab, then "get data", then "launch power query editor", then "New Source", then "other sources", then ODBC, then find your D3 ODBC DSN in the "data source name (dsn)" drop-down. Note that if you're using 64-bit Excel, you'll need the 64-bit D3 ODBC DSN.
------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------
