Page 1 of 1

Sage Job Costing Reports - Unable to connect to datasource

Posted: 20 Jan 2010, 11:25
by Rust
Hi,

The problem we are having is that when you try to create reports, we get the message Report Designer: Unable to connect to Data Source. Check configuration.

Relevant info:
Line50v10
Job Costing v 8.0.0.0032
OS: win7

We have multiple machines with it setup and working currently (and has been working for quite some time). All old clients are running on XP. (installed as clients).

Have tried installing ODBC manually (though it has been unnecessary with all other cases) with no effect.
the system dsn has 1 data source "SageLine50v10" which has datapath ending in Sage\Accounts\ACCDATA

Have also tried uninstalling, then reinstalling both line50 and job costings with no effect.


cheers.

Re: Sage Job Costing Reports - Unable to connect to datasource

Posted: 21 Jan 2010, 17:22
by brucedenney
I suspect Win7 is the problem, you are pushing your luck trying to get it to run on Win7

Sage V10 is end of life.

The issue is most likely to do with the ODBC drivers for JobCosting as you do not report any problems with reports in sage 50.

Is this Win7 64 bit or 32bit?

Sage job costing uses the 32 bit Microsoft Jet (Access mdb) database to report. Have you got 32 bit ODBC drivers installed for Jet/Access/mdb and are they working okay?

Did you do all the Vista installation tricks? Run As administrator and install into a directory other than Program Files?

Re: Sage Job Costing Reports - Unable to connect to datasource

Posted: 03 Feb 2010, 05:35
by rhyven
brucedenney wrote:I suspect Win7 is the problem, you are pushing your luck trying to get it to run on Win7
The issue is most likely to do with the ODBC drivers for JobCosting as you do not report any problems with reports in sage 50.
Is this Win7 64 bit or 32bit?
Hi Bruce,

I managed to get it working here (same place that Rust was talking about above) - Windows 7 32-bit, incidentally. There were a lot of things that I did; I imagine the winning combination is only a subset of the things that I tried, but I don't know which it was. We:
  • Uninstalled both L50 & Job Cost, and installed them in C:\ (avoiding Program Files folder)
  • Reinstalled the ODBC drivers from Line 50\ODBC\Disk 1
  • In the compatibility settings tab (for sgj80app AND RepDes32), I enabled WinXP emulation mode, and gave administrative rights
  • Turned off UAC
  • Plus other things that I unfortunately can't remember
The suprising thing for me though was that it seems 100% of the problem resided in the Report Designer. Once I got RepDes32 'released', everything came right.

Hope this helps someone!
- Eric

Re: Sage Job Costing Reports - Unable to connect to datasour

Posted: 10 Nov 2010, 17:00
by adolauk
Close down jobcosting, hit the windows key (start) and in the search bar type:- ODBCAD32

In the System DNS tab click Add

Select "Microsoft Access Driver (.mdb)"

In data source setup type the following (case sensitive), JobCostingv5

In the desciption type what you like i.e. Jobcosting

Save and exit or apply

Restart jobcosting and you should now have access to reports

Re: Sage Job Costing Reports - Unable to connect to datasour

Posted: 23 Jan 2014, 11:12
by Brennandez
Updating this thread so people know the definite fix, the program has known compatibility issues with W7.

If you get this error, go into the compatibility settings for sgj80app AND RepDes32 which will be in the Sage program folder. Change them so they run as XP service pack 3. Close and re-open the Job Costings software and you'll be able to run reports fine.

Re: Sage Job Costing Reports - Unable to connect to datasour

Posted: 12 Oct 2015, 15:45
by olena.oleary
Brennandez wrote:Updating this thread so people know the definite fix, the program has known compatibility issues with W7.

If you get this error, go into the compatibility settings for sgj80app AND RepDes32 which will be in the Sage program folder. Change them so they run as XP service pack 3. Close and re-open the Job Costings software and you'll be able to run reports fine.
Thanks a lot - its work now!!!