Troble with ASP -> Access -> Sage

[Phil]

My mission is to get some data out of a sage application, via a very
complicated query, into a csv file.

My approach, so far, has been

1) link access tables to the sage application
2) build some sub queries
3) build a big query that brings together all the little queries.
4) dump the data generated by the big query into a csv file.

Hoorah! victory. The above steps all work just fine and the data in
the csv file is as it should be.

The problem is that the whole thing is based on a customer's site and
I need to get that data onto a different server on a regular basis.
So I'm going to have to find a way to automatically generate that CSV
file.

My approach was to write an ASP page that would read the data from the
big query write it to the CSV file. Now that ASP code works just fine
on an Access database that is not linked to Sage. Unfortunately, when
trying to read the linked query the sage driver throws an error.

(Now I'm back in the office, I can't remember what the precise error
was; it was lots of letter and numbers, though!)

Other info: we're running active directory and the only way I could
find to connect to the asp page was to connect using the IP address.
I also did some rooting around on the internet and the only thing that
I found suggested that there was a password syncronisation problem
between the access driver and the sage driver, but didn't offer any
clues as to how to resolve it. I tried setting the passwords to be
the same on both, but still no dice.

So thats the story, now the questions:

1) Any idea whats going on with the ASP -> Access -> Sage thing?
2) If its not an appropriate question for this group, where would I
be best to post it?
3) Is there an alternative way to automatically generate csv files,
with no user input? (could I do it from the command line talking
directly to access?)

thanks for any help you can offer - I'm stumped.

Phil.

[Jeff Cochran]

On 1 Mar 2004 03:01:21 -0800, [email]phil@ideastakingshape.co.uk[/email] (Phil)
wrote:

>My mission is to get some data out of a sage application, via a very
>complicated query, into a csv file.
>
>My approach, so far, has been
>
>1) link access tables to the sage application
>2) build some sub queries
>3) build a big query that brings together all the little queries.
>4) dump the data generated by the big query into a csv file.
>
>Hoorah! victory. The above steps all work just fine and the data in
>the csv file is as it should be.
>
>The problem is that the whole thing is based on a customer's site and
>I need to get that data onto a different server on a regular basis.
>So I'm going to have to find a way to automatically generate that CSV
>file.

It's an Access query. Turn it into a module, run that module from the
schedular service.

>My approach was to write an ASP page that would read the data from the
>big query write it to the CSV file. Now that ASP code works just fine
>on an Access database that is not linked to Sage. Unfortunately, when
>trying to read the linked query the sage driver throws an error.
>
>(Now I'm back in the office, I can't remember what the precise error
>was; it was lots of letter and numbers, though!)

Then it isn't a lot if help is it? Next time, write down the error or
email yourself a Print Screen.

>Other info: we're running active directory and the only way I could
>find to connect to the asp page was to connect using the IP address.
>I also did some rooting around on the internet and the only thing that
>I found suggested that there was a password syncronisation problem
>between the access driver and the sage driver, but didn't offer any
>clues as to how to resolve it. I tried setting the passwords to be
>the same on both, but still no dice.
>
>So thats the story, now the questions:
>
>1) Any idea whats going on with the ASP -> Access -> Sage thing?

Yup. It isn't working. It gets an error of some kind.

>2) If its not an appropriate question for this group, where would I
>be best to post it?

If it's an ASP error, it would be appropriate here. An Access group
could help with other Access related questions.

>3) Is there an alternative way to automatically generate csv files,
>with no user input? (could I do it from the command line talking
>directly to access?)

Yes. See an Access group.

>thanks for any help you can offer - I'm stumped.

Can't offer anything else. No details give to work on, sorry.

Jeff