Problem with ADO call to Oracle procedrue

[mike777]

Hello.
I have a procedure in Oracle that calls another procedure. The second procedure takes a view name, passed as a parameter, and outputs the view to a flat file. Every time I run this procedure in Oracle (using TOAD, etc.), it works fine.
However, when I run it from MS Access using ADO, it works only with certain views. With one view it works fine, with another, it doesn't. It always creates a file, but when it doesn't work, the file is empty.
I haven't been able to find any difference between the views it works with and the ones it doesn't. It just seems random at this point (which, obviously, I don't believe it is, that's why I'm asking!).
Any help is appreciated.
Thank you.
-Mike

 

[Turkbear]

Hi,
Are you using the same username/password combination in TOAD and Access for the connection?

 

[mike777]

Yes, I am.

 

[mike777]

Something else interesting is this:
When I change the script that defines the view that doesn't work to the script of a view that does, it works. So it obviously has something to do with the structure of the view. Mind you, however, that no matter what, it always works from TOAD. Seems very strange to me right now.
I'm thinking it might have something to do with the procedure I wrote to create the flat file, but I'm not sure.
Thanks for the help.
Any ideas at all are appreciated.
-Mike

 

[mike777]

Don't think it has anything to do with the procedure that creates the flat file. If it did, it would be with the column names (I just recently modified the export procedure to accept column names demarcated with double-quotes; as in "Col 1","Col #2", etc.).
I just changed the column names in a view that doesn't work to the same as the names of columns in a view that does work, and it had no effect.
-Mike