![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
Greetings, When you say the stored procedure runs fine, do you mean it runs fine in Access? Or it just runs fine in Sybase? Does the procedure run in Access? Or do you mean the passthrough query runs OK? If the passthrough query runs OK, then I would try an Insert Into statement instead of a Select * Into statement. The only catch is that you have to manually create the table to Insert Into first. DoCmd.RunSql "Insert into yourmanuallycreatedTbl Select * from passthroughQry" Rich *** Sent via Developersdexhttp://www.developersdex.com*** |
#4
| |||
| |||
|
|
On 23 Jan, 18:13, Rich P <rpng... (AT) aol (DOT) com> wrote: Greetings, When you say the stored procedure runs fine, do you mean it runs fine in Access? *Or it just runs fine in Sybase? Does the procedure run in Access? *Or do you mean the passthrough query runs OK? *If the passthrough query runs OK, then I would try an Insert Into statement instead of a Select * Into statement. *The only catch is that you have to manually create the table to Insert Into first. DoCmd.RunSql "Insert into yourmanuallycreatedTbl Select * from passthroughQry" Rich *** Sent via Developersdexhttp://www.developersdex.com*** Hi Rich The SP runs fine in both Access and Sybase, I will try your suggestion of the INSERT sql statement and get back Thanks KC- Hide quoted text - - Show quoted text - |
![]() |
| Thread Tools | |
| Display Modes | |
| |