| Author |
 Topic  |
|
|
Cliff
Average Member
United States
501 Posts |
 Posted - 02 July 2004 : 22:55:04
|
I am using MS Access to administer my MS SQL database. I know it might not be the best way, but it will work well for me.
I just logged on for the first time and got this message:
The Visual Database Tools within Visual Studio 6 and Access 2000 do not support some new features of SQL Server 2000. Because you are manipulating an object in a SQL Server 2000 database, some operations will be unavailable to you. In rare cases, you might not be able to save the database object you modified. In other cases, you will be able to save the object, but its previously existing settings for features new to SQL Server 2000 will be lost. In most of these cases, you will be warned if the Save operation will eliminate existing settings or property values.
Has anyone seen this? If I update to Access XP, might that go away? I am using Access 2000 now.
Thanks. |
|
|
seven
Senior Member
USA
1037 Posts |
|
|
Doug G
Support Moderator
USA
6493 Posts |
Posted - 03 July 2004 : 21:59:22
|
Update MDAC on you adp computer.
I use access projects often to admin remote sql databases. Mostly it works real well, but occasionally connections to the sql server seem to drop and I have to reconnect.
|
======
Doug G
======
Computer history and help at www.dougscode.com |
 |
|
|
Cliff
Average Member
United States
501 Posts |
|
|
Cliff
Average Member
United States
501 Posts |
Posted - 08 July 2004 : 14:27:55
|
I'd use Enterprise Manager, but every time I try to install the eval version, I get an error of there is not enough space on the C drive, free up 436 MB of space. I have over 4GB free. This is not making me happy  . |
https://squarewheelscycling.com/
https://www.pathlabtalk.com/ |
|
|
|
Cliff
Average Member
United States
501 Posts |
|
|
Doug G
Support Moderator
USA
6493 Posts |
Posted - 09 July 2004 : 02:19:03
|
If you haven't, make sure your Access 2000 is fully updated with SR-1, SP-3 and any other updates. One of the office updates makes the sql server 2000 warning go away.
|
======
Doug G
======
Computer history and help at www.dougscode.com |
|
|
|
Cliff
Average Member
United States
501 Posts |
Posted - 09 July 2004 : 12:47:06
|
Thanks Doug. I was not able to update my Office 2000, it was installed by our IS, and Microsoft did not allow updates. I installed my Office XP and the error message is gone now.
The bigger problem is that if you don't define a primary key then you can't edit the data. If there was a pk in Access, you need to reset it in SQL (I do it using Project).
The even bigger problem is when there was no pk in Access, you can't add one later. I'll simply upload new table when I am done with the site. This will be a pain, but oh well. |
https://squarewheelscycling.com/
https://www.pathlabtalk.com/ |
|
|
|
Doug G
Support Moderator
USA
6493 Posts |
Posted - 10 July 2004 : 01:32:46
|
| If you are using an access project (.adp) there is no data in the access file. The adp is only a front-end for the sql server database. |
======
Doug G
======
Computer history and help at www.dougscode.com |
|
|
| |
Topic |
|
Topic Locked
