GeekZilla
Registered: 07/28/09
Posts: 20
|
|
|
Reply with quote | #16 |
Hi Gerard-
Let me see if I understand your suggestion:
Create a new empty database in SQL Server (call it db2)
Copy the contents of the original db (call it db1) to db2.
Run the app wizard and select db2.
Let the app wizard begin generating and see if it successfully generates stored procedures.
Is that what you had in mind?
|
| |
Gerard
Registered: 12/08/04
Posts: 516
|
|
|
Reply with quote | #17 |
Correct. basically the idea was to see if it was a permissions issue as sql server or the access front end will throw error messages if it doesn't like something and give you clues where to go. Also if you have been working on database a bit it is possible that fingers get in the way and finding issue is really hard. this way generally get you back to normal. Rename when happy
Gerard
|
| |
GS2
Registered: 06/07/06
Posts: 68
|
|
|
Reply with quote | #18 |
Hi, I had this error yesterday when trying to rebuilld after changing views...
here is how i corrected it.
Bascially i gave the database Connection user, Server DBcreator rights and then went in to each views with Ironspeed and unchecked the allow insert, update and delete box.
Once i had done this i could then regenerate the Stored Proces and i was able to update the Sql Server side of things
Finally Build the app so that the base classes will be updated and then go back over youre views and check the insert, update and delete box when required.
Rebuild again and you shoul dbe back to where you where before the errors started.
|
| |
GeekZilla
Registered: 07/28/09
Posts: 20
|
|
|
Reply with quote | #19 |
Hi GS2-
Thank you for responding. I was hoping you could answer some questions to help me understand the problem better.
Are you using SQL Authentication or Windows Authentication? Also, can you tell me where you change the View settings for insert, update and delete? I haven't had any views in this application until yesterday and knowing how to change those settings would be helpful.
Really glad you were able to solve your issue!
|
| |
GS2
Registered: 06/07/06
Posts: 68
|
|
|
Reply with quote | #20 |
I am using a sql User...that permission are in sql security under logins..
Within Ironspeed there is a Left hand Tree, at the bottom is the databases node...
Simply start expanding the database structure and clikc on one of your views... on the right hand side you will see the configuration properties screen.
Look down at the borrom of the page you will see the Allow, insert Update and Delete check box.
remember the view will need a Virtual Primary Key before generating base classes for events insert update and delete.
Hope that helps.
|
| |
GeekZilla
Registered: 07/28/09
Posts: 20
|
|
|
Reply with quote | #21 |
Thanks GS2. The check box was staring me right in the face.
Also, thanks for the feedback on how you are authenticating. In my case I am using windows authentication and my account has sysadmin privileges to the SQL Server.
|
| |
RSS(.NETCodeGenerationIsHere).gif)
