Recent content by MadPiet

"Normalization to DKNF is something that I won't worry about until later" -- that's a huge red flag right there. If you do it up front / on paper before you build anything, it saves a ton of time later on. I think I'll just quietly back away from this one... Sounds like volcanics... Oh right...

Why even use a recordset? if it's always true that the only records where the DogID value is null are for the current DogID (in the form(?)), then just use an update query UPDATE tblDNAProfile SET DogID = @DogID WHERE DogID IS NULL; then maybe you'd have to do something silly like use REPLACE...

What IS this? WHERE (((RTGST.RTGSUTR1) Is Null) AND (Not (RTGST.RTGSMailToHO1) Is Null));??? Why make simple things so difficult? One: remove all the parentheses. You don't need ANY of them. WHERE RTGST.RTGSUTR1 IS NULL AND RTGSTT.MailToHO1 IS NOT NULL yup. super hard.

The normal thing to do is to have a reserved range of IP addresses for shared resources like servers, routers, printers etc. Then just the clients (non-server computers) use dynamic IP addresses. I think your network configuration isn't right.

In invisible ink, so nobody can read it. Here's the data as described in his first post. /* I have fields named for each of several companies. Imagine Progressive, National General, Geico, Safeco, Liberty Mutual. Each field is currency, and will contain the quote received from each of them...

Final Answer: /* I have fields named for each of several companies. Imagine Progressive, National General, Geico, Safeco, Liberty Mutual. Each field is currency, and will contain the quote received from each of them. What I'm trying to accomplish is to compare those five fields and find the...

Lemme try this again... Now that I have table definitions... use tempdb; go /* I have fields named for each of several companies. Imagine Progressive, National General, Geico, Safeco, Liberty Mutual. Each field is currency, and will contain the quote received from each of them. */ /* SETUP */...

Oh, MajP brings up a significant point. If your database is properly designed and you want to add a "feature" (something like a set of tables, some queries and some reports in order to answer a specific set of questions), then the expansion is easy. You just have to look at the database ERD and...

Maybe post your proposed table definitions before you go too far. Better to have your design proofread before you spend a ton of time building on top of something that's not going to serve you very well long term. As they say "an ounce of prevention..."

Since I don't know your exact structure, but I've dealt with this before, I'll use my example. A long time ago, I inherited a database where my job was basically to do frequency counts of symptoms and grades. (like the drug ads on TV that say "common side effects include mild [symptom]...") What...

Maybe post your design. Just an empty database. The thing I'm afraid of, having worked with messes like this, is that answering a simple question with a database that isn't designed correctly can be really hard. When I used to do this with databases I inherited, I'd map out the limitations of...

Any chance you could post CREATE TABLE and INSERT scripts with dummy data so we can try out some solutions? You like tested answers, right? SELECT c.CourseID, COUNT(e.*) FROM Courses c LEFT JOIN Enrollments e ON c.CourseID = e.EnrollmentID

no need for the Import Export wizard. I'd use BULK INSERT for that. It's crazy fast. SSIS in this case is overkill I think. If you create a format file, you're sorted. I imported something like a 10 GB file in less than a minute. (I'd skip the indexing until after the table is populated.)

Did you repoint the Access database front end to the MySQL backend yet? Does it work?

ASP? (Honestly, I don't know. That's the kind of thing I'd ask Albert Kallal about.) I'm not an ASP/.NET person, but Albert should be able to help you out.