As with just about anything licensing related - I would advise you call the Product Services line to confirm.

That being said - per the "how to Buy" FAQ (this is...

You might care to look at OPENQUERY over a linked server connection. OPENQUERY will "send" the execution to the remote 2005 server, and bring back the output.

I can't help but thinking that cross applying an aggregate query has got to be murder (especially an aggregate query CROSS JOINED to yet another aggregate query, and then pollenated...

Actually - SQL 2005 is smart enough to be able to do query-level recompiles. So - if your procedure does a bunch of things, one of which happens to...

Two smallish comments:

- the PRINT may truncate the output, but executing the variable should execute the whole thing.

- You'd be better off using NVARCHAR, since both EXEC and...

Your best bet is going to read up on using the ADO command object. It's by far the easiest way to execute a remote SP from a traditional MDB...

That's the thing about a hash function. They're usually functions that even if known are very difficult to reverse. It's not a reversible thing (it's technically not encryption,...

Do you have code in your .NET code to disable the submit button on click? Could it just be someone double-clicking the button/resubmitting whatever they're doing?

Your stored proc makes no...

What I'm trying to get at is someone somewhere is trying to validate the password during login. The most common way to do this is to use the same...

Just be sure NOT to ignore any of the prompts you might get about "show my the primary key/unique value combination" (I must admit to not remembering what the actual...

Look for the Linked Table manager within the Access DB. Should allow you to redirect "regular" linked tables, assuming nothing in the code is updating them (there were various...

What are you using to check the hash code? There were some undocumented procedures floating around on how to do that, but those have been notoriously "flaky" since the...

The question in my mind is - why limit the T-log size? If you happen to have a large table, then that alone could be killing your t-log space.

Also...

RBarryYoung (2/23/2009)

---

Yeah, they tend to say that because Microsoft says it. But Microsoft never explains why they say it, except as part of the general "Surface Area" security policy....

You're also going to need to make sure that your security mapping is correct (meaning - the SQL user being used to do the work from Access needs to be...