What to do? Apparently, use assignment, call, increment, decrement, await or new as a statement. :-)
Please, what's the use of telling us an error message without showing some code causing this message? But, more importantly, why creating things like "Data Access Layer" without knowing the basics of language and having most basic skills? Fundamental things are best learned on the simplest samples, not on real projects.
Where we face such exceptions. Well, "reverse-engineering" your error message into your error would be quite pointless, but, in this case, pretty funny. How can we even managed to write a non-statement and cause this error? Apparently, where a statement is expected. Let's see:
static void Foo() {
Foo;
}
or, say,
static class MyClass { }
static void Foo() {
MyClass;
}
Something like that. (The word "static" is added only to extend the number of possible contexts where exactly these error messages should be expected.)
But if I also had to explain what's wrong in these pieces of "code", I would be talking to a wrong listener. Indeed, when one face such mistakes? When one simply enters code fast and nearly accidentally clicks "Build" before a line if complete, otherwise this is the person having no clue what she/he is doing; only then such questions may be posed.
—SA