B
Barry Ray
We have just upgraded from Small Business Server 4.5 running SQL Server 7 to
Small Business Server 2003 running SQL Server 2000 and have discovered the
following problem on NT4 workstations running Access 2000 adp applications
connected to the new network:-
Stored Procedure names are listed in the database window with the suffix ;1
(e.g. a sproc with name 'sp_Clients' is listed as 'sp_Clients;1')
This means that none of the forms based on Stored Procedures work and it
doesn't seem possible to view the procedures in design view or even to
design a new one. (All other objects, such as Views, seem to behave as
expected)
The NT4 workstations all have SP6a installed and the adp application was
recompiled and reconnected to the new server before distributing to the
workstations on the network. This problem doesn't occur on any Windows 2000
or XP workstations running the same application and connected on the same
network.
I've tried to search for some information on this in the MS Knowledge Base
but haven't turned anything up yet. If any one can shed some light on this
matter it would be most appreciated!
Thanks
Barry Ray
Small Business Server 2003 running SQL Server 2000 and have discovered the
following problem on NT4 workstations running Access 2000 adp applications
connected to the new network:-
Stored Procedure names are listed in the database window with the suffix ;1
(e.g. a sproc with name 'sp_Clients' is listed as 'sp_Clients;1')
This means that none of the forms based on Stored Procedures work and it
doesn't seem possible to view the procedures in design view or even to
design a new one. (All other objects, such as Views, seem to behave as
expected)
The NT4 workstations all have SP6a installed and the adp application was
recompiled and reconnected to the new server before distributing to the
workstations on the network. This problem doesn't occur on any Windows 2000
or XP workstations running the same application and connected on the same
network.
I've tried to search for some information on this in the MS Knowledge Base
but haven't turned anything up yet. If any one can shed some light on this
matter it would be most appreciated!
Thanks
Barry Ray