I downloaded http://msaccess2.net/ORM-10-29-2005.zip and wasn't able to see any of the changes that would support this. While, I am also not using SQL Server 2005 in my projects at the current time, it is probably that in the near future so I would be willing to help you with your issue if you need assistance.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
So, Did anything happen with the proposed update? I could use it too I think.
I succeeded in resolving the issue once by unchecking the required box in ORM.NET
but for some unfathomable reason I can't make it work again. I don't have
much hope for a reply looking at the dates above... Maybe I will try Codus.
they have an active discussion going on.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It does not support different SCHEMAs in database i.e it only supports one default schema in SQL Server 2005 - dbo.
Can anyone tell how to implement the schema support in ORM.NET?
In my view, if [SCHEMA_NAME].[TABLE_NAME] scheme is used instead of using [TABLE_NAME] in generated querries (in FROM clause) this problem can be solved. Any comments on solving this problem???
I'll be thankful.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For those interrested, i've modified the source to support SQL 2005 RTM. (fixed a problem with identity columns).
It's a Visual Studio 2005 RTM project. you can download it here:
http://msaccess2.net/ORM-10-29-2005.zip
Have fun,
Flores
Flores
Could you please post the code lines, class names, procedure names that you have changed in order to solve the "IsIdentity" issue?
Cheers
Ariyawansa
I downloaded http://msaccess2.net/ORM-10-29-2005.zip and wasn't able to see any of the changes that would support this. While, I am also not using SQL Server 2005 in my projects at the current time, it is probably that in the near future so I would be willing to help you with your issue if you need assistance.
The change is not in the code.. but in the sql statements in the resource files
Flores
Cool. Thanks mate. I spend good hours to figure out a way to solve the issue.
Cheers
Ariyawansa
Hi this is great news. I am facing this problem now. I am using ASP.NET 1.1 with SQL Server 2005. Does your version work with my settings?
I hope you got the VS 2003 version of this fix. Coz I really need it, and I do not have VS 2005
I can see if I can take a look at doing a 2003 version of the fix. What is your email so I can email you the zip file?
MY email address is parseghian@gmail.com
Thanks a lot for doing this, it is very urgent.
Hi, any updates on the issue? No intention to put pressure on you, but my project is on hold waiting for your fix. Thanks,
So, Did anything happen with the proposed update? I could use it too I think.
I succeeded in resolving the issue once by unchecking the required box in ORM.NET
but for some unfathomable reason I can't make it work again. I don't have
much hope for a reply looking at the dates above... Maybe I will try Codus.
they have an active discussion going on.
It does not support different SCHEMAs in database i.e it only supports one default schema in SQL Server 2005 - dbo.
Can anyone tell how to implement the schema support in ORM.NET?
In my view, if [SCHEMA_NAME].[TABLE_NAME] scheme is used instead of using [TABLE_NAME] in generated querries (in FROM clause) this problem can be solved. Any comments on solving this problem???
I'll be thankful.
Hello there,
I am unable to download the fix.
How can I get this fix?
Thanks