Search results

As an Access developer who uses SQL Server exclusively, and is a big proponent in this forum of using it, everything Galaxiom has said is true. You have to learn to think differently about how to architect an app. You have to learn T-SQL, and how and when to use the various SQL Server things...

I have too. I've evaluated many database applications for clients from a correctness of DB design perspective. There are some real losers out there. It's proof that one can sell crap to unsuspecting customers if that's how one rolls.

Peter, yes, walk away I think. Even small businesses have expenses. Do they get their electricity for free? Of course not. Nor should they get their data management for free.

I looked at the Andrews CWH table, and this is pretty easy to sort out. The business object looks like what I've seen when a product is built from components, and called an assembly. The CWH table has poor logical and physical design, and it will take more than a couple of days to refactor it...

First off, a table with 60 columns is suspicious, and likely a candidate for redesign in order to normalize it. Want to post the table design?

The benefits are just what I said - Views, Stored Procedures, Triggers, Scheduled Jobs, real batch processing, Transact-SQL. Many things of real value. It's actually possible to build a two-tier client server app with a fairly light client. Those benefits don't necessarily go to an existing...

If you have the opportunity to move to SQL Server, consider that the benefits go on forever, and the cost is a one-time thing. Using Access as a RAD tool against SQL Server is SO MUCH better than a pure Access environment. Views, Stored Procedures, Triggers, Scheduled Jobs, real batch...

As I said, if specifying multiple columns in a SQL ORDER BY clause breaks your code, your code is too brittle. Throw it out. Write code that doesn't choke on common SQL statements. I hate to be so terse about it, but if a class module, or function, or even code behind a form dies because of a...

If something as commonly done as adding an ORDER BY Clause to a SQL statement "tosses a wrench" into code, I would declare that code overly brittle, scrap it, and rewrite. We order datasets using SQL all the time in database development, and in a well architected app, this causes no trouble...

I'm an ANSI 92 SQL guy. Access may have some oddity that allows you to do this. I don't know of it. It's really not that hard, in fact easier than replying to this thread time-wise, to just add the ORDER BY clause to your SQL statement. You can have multiple columns in your ORDER BY clause, so...

Nope, not how it works. Just add an ORDER BY clause that specifies the columns you wish to use to your SQL statement. Presumeably the same columns as you have indexed. The order of the columns in your ORDER BY clause will affect the output.

What you want is a DSN-less connection. Here's an MSDN article. There are plenty of other articles out there on this. http://support.microsoft.com/kb/892490

Yep, it reveals the password. But my database is in the cloud, so I can't use Windows authentication. In a production environment, this would be fine because we would all be following best practices and using mixed-mode authentication, with users authenticated by their domain login. So no...

Yes, this is likely the real issue. There are probably several business objects represented in his table.

For larger projects, yes. These are preliminary design activities you are talking abut. Application architecture is important. Project management is important. In most organizations, IT has a yearly budget, and a project only gets approved if it has good ROI. Can't know ROI unless you know the...

SELECT (some stuff), TotalHoursLevel = CASE WHEN TotalHours <= 15 THEN 'Level1', WHEN TotalHours > 15 THEN '15-1' END, Level2 = TotalHours - 15, (if I understand what you mean) (select more stuff) FROM SomeDamedTable WHERE...

Coming to SQL Server with no knowldedge of it as I also did, it took me about two months to get up to speed. I had large database experience (Progress), so I had all the concepts of how to design databases with millions of rows. The benefits of moving data processing off to SQL Server are...

Binding a stored procedure to a form is probably impossible. Here's how I'm using basic SQL Server objects from Access. SQL Server tables I link to my Access front end. I use them as recordsources for forms. The same with views, although I mostly use views for reports, again to keep the data...

I think this merits a build-versus-buy analysis. There have got to be a bunch of web-based apps out there that track a person's hours working with each of several clients. Maybe look into an app for attorneys to track their time with each client. They typically track time in 15 minute...

Probably, the query does not include the primary key for both tables. It needs to be present for the query to be updateable.