Hi, all! We’re working on an axapta 3.0 SP1 system for our customer. In order to test our development, we got the customers databease, which we restored here (SQL Server 8.0). That’s where the trouble started: First of all, the tables belonged to different users: dbo, sa, bmssa. Any program worked with that databes, but not axapta. So we copied the database to another one, where we created the tables correctly with the correct user (as sp_cahngeowner etc. did not work). The help form the support (?) was also great: they managed to compy each and any database table to have the same name but belongs to a different user. And, of course, the new tables were completely empty - they’re funny clowns [:o)], aren’t they? Now after many try-and error e managed to make axaprta accept the database. Unfortunately there seems to be one more problem: We can’t open any form, because the access to SysSecurityFormTable fails. The error message is: SQL-Fehlerbeschreibung: [Microsoft][ODBC SQL Server Driver][SQL Server]Konflikt der Sortierung für die equal to-Operation kann nicht aufgelöst werden. I’ll try to translate it to english (sorry, only very free [:D]translation): “Unable to resolve sorting conflict for the equal-to operation” Looks like we’re having different sorting settings. But on our development database we’re having the same settings and no problems at all. A last piece of information: The table in question is completely empty, as we can see from the enterprise manager of SQL server. Can anyone give me any hints? Thanx!
Hello, I’m no expert on SQL, but this is my ideas. First of all, when restorting Axapta databases into SQL, you have to restore Master database also, in order to get the user rights to work. When I had trouble with a Axapta database in SQL and needed to transfer all data into a new database I did the following. 1. Create new database “Ax2” and set bmssa as owner. 2. Start Axapta on Ax2, the setup guide will create all tables. It’s important to configure Axapta the same way the customer, so that all needed tables are created. 3. Run a script to delete all data in Ax2 (except tables Sql*) to aviod duplicates later. 4. Now we have one empty database (Ax2) an the old corrupt database (Axdb). In SQLManager now copy data (only data) from Axdb to Ax2. 5. All done. The reason i din’t copy tables as well in 4 is that i wanted a different sortorder on the tables in Ax2. The senario above was used by me in a test/demo enviroment, and I don’t recomend to use it in a customer enviroment if you’re not sure it’s the only/right way. /Peter Karlsson