Member Login

Username
Password
Forget Password
New Sign Up
Search Forum

Buy Support
Incidents

If you can't find your answer in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us private or confidential information:

Click Here
If you can't login and post questions or you are having trouble viewing forum posts:
Click Here
Callback
Support

If you live in USA, UK, Canada, Australia or New Zealand, you can leave us details on your question and request us to call you back and discuss them with you personally  (charges apply).

Click Here
 
Buy Support
Incidents
If you can't find your answer in the FREE PUBLIC QDeveloper Forum, require URGENT Priority Support, or you need to send us private or confidential information:
Click Here

Forum : Access Stack OverflowSearch Forum

Forum Home > QODBC - ODBC Driver for QuickBooks > QODBC v8 Forum

 New Topic 
 
 Post Reply 
[1]  
 Access Stack Overflow 
 Author   Message 
  SLS 
  
 Group: Members 
 Posts: 11 
 Joined: 2008-01-30 
 Profile
 Posted : 2008-08-27 01:49:01

I know this isn't an ODBC issue, at least I hope it's not, but I have a client that is blaming ODBC and I can't disprove them.

If I create a report in Access 2003, and then the client tries to run it in Access 2007, they get a Stack Overflow error. I can run the same report on my machine with Access 2007 and it works fine. I'm saying it's a memory issue with their system, they say it's the report. Has anyone else run into this and can anyone tell me where to look to fix whatever is the issue?

Thanks

 

  Top 
  Tom 
  6c3c1_sdk-qodbc.gif
 Group: Administrator 
 Posts: 5510 
 Joined: 2006-02-17 
 Profile
 Posted : 2008-08-27 08:19:22
If I remember correctly, this happens when the .mdb is moved to another location. Try copying the .mdb to the same drive and folder as you have on the client's system.  

  Top 
  SLS 
  
 Group: Members 
 Posts: 11 
 Joined: 2008-01-30 
 Profile
 Posted : 2008-08-29 01:32:22

Thank you for your responce Tom. I tried creating the same series of folders on the clients machine and the same error happened. However, when I went back to my systems and tried actually moving the files from one machine to the other, not sharing them from the first system, it hit me. (Like a load of bricks.) The system I use to create the databases is a dual boot system....I wasn't on the C drive but the E drive. Kind of hard to recreate the folder location when the drive is different.

I'm now in the process of moving and recreating files to the system with only a C drive on it to avoid further issues. Once I've recreated everything on a C drive I'll try the clients again, something tells me it'll work. If not, I'll let you know.

Thanks again.

 

  Top 
 New Topic 
 
 Post Reply 
[1]  

Jump to