Why are my stored procedure renamed "Proc;1"? 2

[Thom]

Thanks in anticipation...
I have an .adp where I connect to an MSDE sql backend. A number of networked PC's connect to this MSDE datasource. All PC's can see and connect to the sql server. However, when I open the .adp, a number of the computers rename all the stored procedures (Office 2000) with an ";1" suffix thereby rendering the file useless i.e. Storedproc;1
I am at my wits end (and client also) to find the cause of this anomaly.
Any help ????

Regards
Thom

 

[grtammi]

Are the tables linked into a front-end, or are your users simply connecting to the back-end? You get more than one user connecting directly to the back-end at the same time, and that MAY cause the renumbering of the procedures ...



Greg Tammi, IT Design & Consultation
Work:

http://www.atsbell.com

Home:

http://members.shaw.ca/gregandliz

 

[Thom]

Thanks Greg,
The problem exists whether it is one user or many - it appears to be specifically related to the users computer - one PC in an office will see the correct Stored procedures and work correctly, while another in the same office renames them to StoredProc;1
In our development environment we use four PC's to emulate a multiuser environment and all works perfectly. I suspect that it may be a bug (SP issue with Microsoft) and the versions that have been installed throughout the company. Finding the 'bug fixes' for Office 2000 or Access 2000 inside of Microsoft will be my next 'port of call'.
Thanks again Greg - a weird one!

 

[PaulBricker]

http://msdn.microsoft.com/vstudio/downloads/addins/MSDE/techfaq.aspx

This link is to MSDN library for MSDE 1.0 which is probably what you have with Office 2000
Here is one of the faq's that might impact you

Q.
Can MSDE 1.0 databases serve multiple users?

A.
MSDE 1.0 is tuned for desktop and shared solutions where there are fewer than five concurrent workloads hitting the database at any one time. If your solution needs to support more than this number of concurrent batches, you may need to migrate to SQL Server or SQL Server Enterprise editions for optimal performance at this higher level of scalability.

You don't say how many users you have on the network but it could be part of the problem that your test network would not have picked up. Also, MSDE 1.0 is not as good as MSDE 2000 which come with Office XP (at least that is what I hear). I'm using 1.0. There are supposed to be some Service Packs out there for SQLServer 7.0 that you can use with MSDE 1.o also. The link above may help.

Paul

 

[cmmrfrds]

There is a service pack that you need to install. I don't remember off the top of my head the number, but it was addressed a few/couple of months ago in a thread. I will see if I can find the thread.

 

[cmmrfrds]

It is a service release on Office 2000. Check the microsoft site at

http://www.microsoft.com/downloads/...03-7633-45B4-AB96-795EE656F2A2&displaylang=EN

 

[PaulBricker]

You might check out SP2 for Office here

http://www.microsoft.com/downloads/...81-BB61-4364-9E56-5C07D4DABC38&displaylang=en

I haven't read any of the articles but it does indicate some upgrades for MSDE.

Paul

 

[Thom]

Thanks all,
I have discovered that you must load/ensure that all the machines using the 'client' (Access adp ) have Microsoft Office Service Release 1/1a applied (for Access 2000). Older releases of Access were released before SQL Server 2000 and hence incompatible.
Microsoft mention that even though SP3 has been applied, it needs to have 1/1a installed.
For additional reference....

http://support.microsoft.com/default.aspx?scid=kb;EN-US;326585

Hope this will help others in dire straights.
Thom