Viewing 15 posts - 1 through 15 (of 22 total)
Select * from Table_Name where TownName=:TownName
Where :TownName is a paramter to which you must assign a value in your Access app. I would suggest that you avoid filters such as...
April 7, 2005 at 8:06 am
Excellent article. I have tinkered for quite some time with a QA alternative, and the thing that has bugged me most is the generation of SQL statements. This article has...
February 14, 2005 at 1:56 am
When connecting from a piece of custom software, i am accustomed to building the connection string myself, and then judiciously using the Trusted_Connection property as I need to, but...
February 1, 2005 at 11:57 pm
Damn!! I never thought of that. Thanks. I'll give it a try.
November 12, 2004 at 8:52 am
No. AS per usual, there was no maintenance plan in place. But obviously there is now. Amazing how the door is always bolted after the horse has bolted, isn't it?
September 18, 2004 at 2:47 am
My approach would be different in that I would continue to use the replication stored procedures on the subscriber server, but I would edit the delete stored procs to take...
August 18, 2004 at 4:53 am
We wrote a solution similar to this for an International NGO about two years ago. Basically, we could not use anything like Replication or DTS, as all of the sites...
August 13, 2004 at 8:58 am
Yes. Add the oclumn using the repl stored procs or EM Repl tools, but add the default contraints directly in the table editor in EM or via queyr analyser. That...
May 26, 2004 at 3:15 am
Nope. Never got that far. If I was going to drop a column at the publisher, I first dropped the default constraint at the subscriber. Simple.
May 25, 2004 at 9:30 am
I bumped up against this problem a short while ago on a project. I eventually concluded that the problem occurs because the default constraint is given an arbitrarily assigned name...
May 25, 2004 at 3:42 am
Or you can use parameterization to achieve the same tadk. Here is an example from BOL:
sp_executesql supports the setting of parameter values separately from the Transact-SQL string:
DECLARE @IntVariable INTDECLARE @SQLString...
March 29, 2004 at 1:20 am
Ah, humble apologies I guess it helps to ask for more info before jumping to design conclusions. What you say makes absolute sense....
March 12, 2004 at 10:04 am
It sounds to me like you have data redundancy in your database design. If possible it might be better to look at further normalising your design to eliminate the problem,...
March 12, 2004 at 9:31 am