SQL Server Error on Field Rename

sgg
Member Posts: 109
Setting :
Attain 3.70 B Client Running on SQL
Issue :
After Renaming a field in a Table, I could NOT save the Modifications made. I get the following error:
The following SQL Server error(s) occured while accessing the Employee Table:
15333, "42000",[Microsoft][ODBC SQL Server Driver][SQL Server] error: The qualified @oldname reference database(DatabaseName) other that the current database.
Attain 3.70 B Client Running on SQL
Issue :
After Renaming a field in a Table, I could NOT save the Modifications made. I get the following error:
The following SQL Server error(s) occured while accessing the Employee Table:
15333, "42000",[Microsoft][ODBC SQL Server Driver][SQL Server] error: The qualified @oldname reference database(DatabaseName) other that the current database.
Sunday, Godwin G
0
Comments
-
I've seen that error where the customer was on SQL and we developed on C/SIDE. For some reason there's something that doesn't go together well. I think we just created our own SQL database and redid the development.0
-
In this case, I am Developing in 1 Database (SQL database).
But I could not save the Table after Renaming the Field.
The system did not allow the modification made.Sunday, Godwin G0 -
Hello the problem is that when you select your database name, navision is not case sensetive, but when you try to rename a field SQL errors because it's case sensetive.
Please close the database. login again and do a lookup on database and and select the database. This way you have selected the right name with correct case. Now you can rename fields.0 -
Thanks ara3n
I will try what you suggested.Sunday, Godwin G0 -
What about recompile all objects?
Or try to disable all keys, save, enable them... to recreate the SIFT triggers on the table...0 -
Thanks ara3n,
your suggestion to Login by Using the Lookup to DatabaseName rather than typing the DatabaseName WORKED.
=D>Sunday, Godwin G0 -
you welcome. Ran into the same problem programming on site, working on sql. It's not the lookup that you have to do. Just make sure the database name is in correct case.0
-
[Topic moved from Navision forum to SQL General forum]Regards,Alain Krikilion
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions