• Announcements

    • turbofandude

      Proper Problem Reporting for the TFDi Design 717   07/09/2017

      Folks, As the user count is increasing, it is becoming more of a task for us to stay on top of problem reports. We are also receiving an increasing amount of incomplete reports that we are unable to follow up on (which frustrates everyone, us included). On that note, we are going to be enforcing a stricter formal problem reporting system. There are a few main points that need to be addressed. ALL problem reports must be submitted via the Bugs and Suggestions system. Open discussion on the forums is fine, but our team simply cannot respond to every single comment (especially when the majority of doing so is asking for information the Bugs and Suggestions system already asks for). Incomplete reports will be ignored. This means reports like "my FPS is bad" will not be given weight. This isn't because we don't care. It is because a report like that does absolutely nothing for anyone - we can't fix it based on that. Please include EVERYTHING you can possibly think of regarding the problem and take as many steps as you can to isolate it. Prepar3D v4, despite what you have heard, can still be unstable. Yes, it is definitely possible to fly flights without issues. But it is still relatively new, as are most of the addons available for it. Please refrain from attacking us or other developers because of this. We have already had one scenario where a 717 CTD was resolved by an update to Prepar3D itself. This is likely not the only time that will be the case. You are still free to report the crashes, as it may help whoever the developers of the faulting code are solve the issue. Duplicate reports will be deleted/merged. For the sake of sanity for us trying to prioritize and evaluate issues, if we discover multiple reports of the same thing, we may merge/delete the duplicates. We strongly encourage you to search and see if your problem has been reported before. Thank you all in advance. This may seem overbearing, but this is the only way we are going to be able to stay on top and continue heading in the direction we, and the community, want.
kymh

P3Dv4 - Error Connecting to Database

Recommended Posts

Again I am writing to you to ask if there is a possibility of solving the problem of the database Microsoft Access database 32 bits since until the moment I still have the problem and when I install the 64-bit database I can not working with the 32-bit office seeing me forced to reinstall the whole Office as it changes the libraries.
Thanks for your answer to know when you plan to solve this as I can not update the program so far to avoid problems
Sincerely
Antoni

Share this post


Link to post
Share on other sites

Hi Guys

Im getting the same errors as the other guys, I have followed the instructions to the T and still no joy

1)unable to load odbcj32.dll

2) Error connecting to database

SQL_HANDLE_ENV(IM004)

Session is not connected P3Dv4.1 no luck in v4 either

Share this post


Link to post
Share on other sites

Hello again:
Having not received a response to my raised question I would like to know if you have any solution to this problem about the 64 bit database in a 32 bit office 2010 environment.
I see that this subject has also been raised by other people with the same difficulty.
After so long without response I still can not enjoy his program and I am quite discouraged and with a sense of abandonment.
I wait for your indications to see to solve this or to abandon definitively by lack of solution.
Thank you very much

Antoni

Share this post


Link to post
Share on other sites

hi Colin,

I see this dragon has reared it's ugly head again in build 1.0.9.14. I needs some assistance to resolve please.  I have teamviewer also. I can PM when your ready.

Share this post


Link to post
Share on other sites
On 10/26/2017 at 9:39 AM, FireRx said:

Disreguard, 

 

I got it going now, thanks. 

 

 

 

What did you do to fix it?  I am having the issue and have not been able to solve it yet.

Share this post


Link to post
Share on other sites

Good afternoon: I have the same problem and it still does not work. Do you have a definitive solution or do I forget about TFDI?
Attached error message
Antoni

 

SOCI ODCB Error
---------------------------
Error Connecting to database: [Microsoft][Administrador de controladores ODBC] No se encuentra el nombre del origen de datos y no se especificó ningún controlador predeterminado (IM002)
---------------------------

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now