ExecuteNonQuery: Connection property has not been initialized

Question

I've seen this question asked here before, but never when Enterprise Library is used. I've used code like the following before and it works fine. What's the problem this time? I get the error on the last line:

    Database db = new SqlDatabase(MyConfiguration.Current.ConnectionString);
    DbCommand cmd = db.GetStoredProcCommand("AddWorkListItem");

    db.AddInParameter(cmd, "@PartNumber", DbType.String, partNumber);
    db.AddInParameter(cmd, "@Quantity", DbType.Int32, qty);
    db.AddInParameter(cmd, "@WorkListTypeCode", DbType.String, code);
    db.AddInParameter(cmd, "@UserKey", DbType.Int32, userKey);

    return cmd.ExecuteNonQuery();

any final solution with full source code sample working about it ? https://entlib.codeplex.com/discussions/288036 — Kiquenet, Oct 30 '13 at 09:29

score 11 · Accepted Answer · answered Aug 24 '12 at 22:05

11

Gosh it's been a while but I'm pretty sure you call db.ExecuteNonQuery(cmd) rather than cmd.ExecuteNonQuery(). Have you tried that?

answered Aug 24 '12 at 22:05

kprobst

16,165
5
32
53

D'oh! Looks like I got my ADO.NET and EntLib wires crossed. Thanks! – birdus Aug 27 '12 at 14:26
Works for me!! but whats wrong with cmd.ExecuteNonQuery()? – Fresh Saint May 04 '15 at 11:27

ExecuteNonQuery: Connection property has not been initialized

1 Answers1