Viewing 15 posts - 91 through 105 (of 252 total)
I should have said this is running on an old SQL Server 2000 box. Will your solution still work?
September 3, 2014 at 11:23 am
I believe option 1 will work. I'll kick the tires.
July 30, 2014 at 4:39 pm
Most of our stuff was converted to a COTS product, but we still have a few legacy apps that use Access as a front end.
I worked on these many years...
December 26, 2012 at 10:20 am
It was the &&**( shift key. All is good now.
Access is not my friend.
December 24, 2012 at 12:41 pm
We are not using cmd shell. Rebooting stopped the process. Maybe the index defrag is hogging too many resources?
March 21, 2012 at 2:45 pm
That is a good start. Still rather mysterious...
March 21, 2012 at 1:03 pm
Thank you! Glad brilliant peoples still troll this website.
February 7, 2012 at 3:21 pm
I installed the 64 bit native client for SQL2005. This did not solve the problem.
I ran the app on Windows 2008 32 bit and...
October 13, 2011 at 9:15 am
No I tried installed a 32 bit version of the SQl Client and 2008 R2 would not cooperate. I had to install the 64 bit version of the client.
October 12, 2011 at 2:28 pm
Nope. The app we are using is ancient. What I really wanted was the native client for SQl2005 64 bit. I installed it. ...
October 11, 2011 at 5:27 pm
Yes all we need is the MDAC.
October 11, 2011 at 1:10 pm
I found a blurb from Microsoft saying Server 2000 is not supported on Windows server 2008 R2. This is not amusing.
October 6, 2011 at 12:58 pm
Yes, we will need a DSN. The SQL200 database will be on a different box. We just need to connect to it.
October 6, 2011 at 12:37 pm
Viewing 15 posts - 91 through 105 (of 252 total)