fmorais
25th March 2003, 14:40
Hi,
Following some problems I had, I'm now creating this thread in order to discuss possible causes and the specific functionality of the MSQL driver.
My environment is like this:
BIVc4(Pset 6.1c.06.05)/MSQL2000/Windows2000
In one test I had to make in order to try to solve another problem, I removed the parameter "msql_65_schema:1" from db_resource file.
After removing the parameter I started getting 512 errors following tables (for all companies):
tcedi750
tuddc100
tuddc110
tuddc901
tuxch001
tuxch901
ttaad502
and (more problematic) in company 000:
ttaad321
ttaad322
ttaad410
ttaad502
ttadv304 (big trouble)
ttadv335 (big trouble)
ttadv364 (big trouble)
tttss010
The strangest thing is that the table format is exactly the same. If you remove the parameter, you'll get 512 errors, if you put it again the errors disappear.
What can cause this behaviour? Is it related with the stored procedures created for each table in MSQL?
Will I have to maintain this parameter forever in db_resource, even if using MSQL5000 ?
Thanks
Fred
Following some problems I had, I'm now creating this thread in order to discuss possible causes and the specific functionality of the MSQL driver.
My environment is like this:
BIVc4(Pset 6.1c.06.05)/MSQL2000/Windows2000
In one test I had to make in order to try to solve another problem, I removed the parameter "msql_65_schema:1" from db_resource file.
After removing the parameter I started getting 512 errors following tables (for all companies):
tcedi750
tuddc100
tuddc110
tuddc901
tuxch001
tuxch901
ttaad502
and (more problematic) in company 000:
ttaad321
ttaad322
ttaad410
ttaad502
ttadv304 (big trouble)
ttadv335 (big trouble)
ttadv364 (big trouble)
tttss010
The strangest thing is that the table format is exactly the same. If you remove the parameter, you'll get 512 errors, if you put it again the errors disappear.
What can cause this behaviour? Is it related with the stored procedures created for each table in MSQL?
Will I have to maintain this parameter forever in db_resource, even if using MSQL5000 ?
Thanks
Fred