MSDN Magazine January 2001
View Complete Post
MSDN Magazine April 2001
MSDN Magazine March 2001
MSDN Magazine February 2001
MSDN Magazine June 2000
MSDN Magazine May 2000
MSDN Magazine April 2000
MSDN Magazine March 2000
I'm using VS 2008 and SQL 2008.
I have created the tables and the stored procedures in SQL 2008.
In VS 2008, I created DataSet1.xsd in App_Code and created the connectionString in web.config file.
Then when I go into the DataSet1.xsd and try to add a TableAdapter, strange things happened.
First I chose the data connection, then selected "Use existing stored procedure", then there was nothing listed in the dropdownlists (in Select, Insert, Update, or Delete).
I'm sure the connectionString is correct because if I choose "Use SQL statement" and type in a "select * from mytable1", the TableAdapter can be created without any problem.
can anyone help me in creating BCS entity using BCDM model in visual studio using Linq to sql query for a SQL stored procedure.I am receiving remote debugging
error and few other errors.Your step by step approach helps me a lot,I have been playing with this for long,but still no answer.
I have a very simple Oracle (11g) Stored Procedure that is declared like so:
CREATE OR REPLACE PROCEDURE pr_myproc(L_CURSOR out SYS_REFCURSOR)is BEGIN OPEN L_CURSOR FOR SELECT * FROM MyTable; END;
This compiles correctly. The cursor contains col1, col2 and col3.
In SSRS, i have a Shared Data Source that uses Oracle OLEDB Provider for Oracle 11g:
In Visual Studio 2010, I have a webform, with a button that attempts to manipulate a SQL table that has a lot of data (several years & archives of 12 people's emails: emailID, bodies, to, cc, bcc, date/time). Problem has always been that with so
many emails (500,000), I had to break up the manipulation jobs a bit, or VisualStudio/ASP.Net development server would freeze up running those SQL stored procedures.
So I determined, for each (.pst) email store, a unique series that was in each emailID - for instance, person A would have 00000195195xxxxx as their emailIDs, and person B would have 00000123456xxxxxx as their email IDs - and used those 30 [or so] identifying
flags to recursively call a function that until yesterday was running my SQL stored procedures just fine.
YEsterday, while that was running, for giggles, I rebuilt the index on my table, and freaked out the development server by accident. I had to rollback the database using SQL Server Management Studio, or the database was "Suspect".
Now, my SQL Stored Procedure in that recursively called function won't run, despite the fact that the original SQL Query [that gets the identifying flags into a Datatable, and runs the sproc on each "row"] works just fine.
I think it's a setting, to protect me ... but can't
I'm using Dynamic Data with Entity Framework in VS2010.
Let's say my table has these fields:
MyTableID (PK)PersonID (FK)LocationID (FK)TotalItemsSold
Hypothetical scenario (it's easier for me to explain this way, so just bear with me for now)... But let's say each row in the table represents "how many items were sold by such-and-such employee at such-and-such location," where location and person are foreign keys which are referencing other tables. Basically, there should be no more than a ONE row which has a particular combination of Person and Location. Makes sense?
So, when inserting new rows using my Dynamic Data app, the insert form displays editable fields for Person (dropdown), Location (dropdown), and Items Sold (textbox). How do I prevent users from inserting another row into the table containing an already-existing combination of Person and Location? How do I displaying useful feedback to them in the event that they DO attempt to do this?
I have several thoughts about this, but since I'm new to Dynamic Data, I'm not sure which way to go. For example:
Option 1: Use "cascading dropdowns" approach in the insert form and only pull in the "allowed" combinations of the two dropd