|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
Thread Tools | Display Modes |
|
#1
October 13th, 2008, 05:23 AM
posted to microsoft.public.access,microsoft.public.windows.server.networking
|
|||
|
|||
Propriatpry Access Application and Network Access
We have Proprietary application that created using Access97. It runs on a
P2P nine node network using W2K Pro and XP Pro PCs. Access times are very good for the nine concurrent users. We'd like to move it to the main network (MS Server 2003, one GB fiber back bone, 100BT to the PCs.) we heard from another facility that the application runs slow on the Novell TCP/IP network w/ thirty concurrent users. Is there any reason why the Access97 application would run slowly on a MS Server 2003 network: MS Server 2003, one GB fiber back bone, 100BT to the PC w/ 20 concurrent users? Thanks, Jack 
|
|
#2
October 13th, 2008, 02:11 PM
posted to microsoft.public.access,microsoft.public.windows.server.networking
|
|||
|
|||
|
Propriatpry Access Application and Network Access
Make sure oplocks is configured appropriately if you can't upgrade.
Upgrading the backend to SQL Server or at least SQL Server 2005 Express is the best solution. http://www.microsoft.com/sql/edition...s/default.mspx http://support.microsoft.com/?kbid=296264 http://support.microsoft.com/?kbid=300216#11 http://support.novell.com/cgi-bin/se...?/10085899.htm http://support.novell.com/cgi-bin/se...?/10091561.htm -- Regards, Dave Patrick ....Please no email replies - reply in newsgroup. Microsoft Certified Professional Microsoft MVP [Windows] http://www.microsoft.com/protect "Tom" wrote: We have Proprietary application that created using Access97. It runs on a P2P nine node network using W2K Pro and XP Pro PCs. Access times are very good for the nine concurrent users. We'd like to move it to the main network (MS Server 2003, one GB fiber back bone, 100BT to the PCs.) we heard from another facility that the application runs slow on the Novell TCP/IP network w/ thirty concurrent users. Is there any reason why the Access97 application would run slowly on a MS Server 2003 network: MS Server 2003, one GB fiber back bone, 100BT to the PC w/ 20 concurrent users? Thanks, Jack
|
|
#3
October 14th, 2008, 12:39 AM
posted to microsoft.public.access,microsoft.public.windows.server.networking
|
|||
|
|||
|
Propriatpry Access Application and Network Access
"Tom" wrote:
We have Proprietary application that created using Access97. It runs on a P2P nine node network using W2K Pro and XP Pro PCs. Access times are very good for the nine concurrent users. We'd like to move it to the main network (MS Server 2003, one GB fiber back bone, 100BT to the PCs.) we heard from another facility that the application runs slow on the Novell TCP/IP network w/ thirty concurrent users. Is there a WAN involved on that other network? Multiple buildings located a distance apart? If so that is likely the performance issue. Although there is one reliable report of a 100 Mb WAN working well. Is there any reason why the Access97 application would run slowly on a MS Server 2003 network: MS Server 2003, one GB fiber back bone, 100BT to the PC w/ 20 concurrent users? Have you tested this out yet? Also see the Access Performance FAQ page at http://www.granite.ab.ca/access/performancefaq.htm Tony -- Tony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
|
|
#4
October 26th, 2008, 01:51 AM
posted to microsoft.public.access,microsoft.public.windows.server.networking
|
|||
|
|||
|
Propriatpry Access Application and Network Access
"Dave Patrick" wrote in message ... Make sure oplocks is configured appropriately if you can't upgrade. Upgrading the backend to SQL Server or at least SQL Server 2005 Express is the best solution. http://www.microsoft.com/sql/edition...s/default.mspx http://support.microsoft.com/?kbid=296264 http://support.microsoft.com/?kbid=300216#11 http://support.novell.com/cgi-bin/se...?/10085899.htm http://support.novell.com/cgi-bin/se...?/10091561.htm -- Regards, Dave Patrick ....Please no email replies - reply in newsgroup. Microsoft Certified Professional Microsoft MVP [Windows] http://www.microsoft.com/protect "Tom" wrote: We have Proprietary application that created using Access97. It runs on a P2P nine node network using W2K Pro and XP Pro PCs. Access times are very good for the nine concurrent users. We'd like to move it to the main network (MS Server 2003, one GB fiber back bone, 100BT to the PCs.) we heard from another facility that the application runs slow on the Novell TCP/IP network w/ thirty concurrent users. Is there any reason why the Access97 application would run slowly on a MS Server 2003 network: MS Server 2003, one GB fiber back bone, 100BT to the PC w/ 20 concurrent users? Thanks, I'll check it out.
|
|
#5
October 26th, 2008, 01:52 AM
posted to microsoft.public.access,microsoft.public.windows.server.networking
|
|||
|
|||
|
Propriatpry Access Application and Network Access
"Tony Toews [MVP]" wrote in message ... "Tom" wrote: to the PC w/ 20 concurrent users? Have you tested this out yet? No, not yet. Also see the Access Performance FAQ page at http://www.granite.ab.ca/access/performancefaq.htm Tony -- Tony Toews, Microsoft Access MVP Please respond only in the newsgroups so that others can read the entire thread of messages. Microsoft Access Links, Hints, Tips & Accounting Systems at http://www.granite.ab.ca/accsmstr.htm Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ Thanks, I'll check it out.
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
