|
PIEBALDconsult wrote: I use a UDL file.
Never heard of it, but I'll look it up. In actuality, I'm used to coding db stuff manually, and that's all I really understand, but I thought I'd try out the new toys in VS. Note to self:
Never put your faith in Wizards.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
|
|
|
|
|
Roger Wright wrote: new toys
 Stick with what works.
|
|
|
|
|
I did tonight, and hand coding the connection string - identical to that used in the wizard - worked perfectly, first try. 
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
|
|
|
|
|
PIEBALDconsult wrote: when I am trying to determine a connection string for some new database, I use a UDL file.
Then you sound just the person to answer this[^] question.
It's time for a new signature.
|
|
|
|
|
Or maybe not... I only use the UDL file to get the connection string -- then I do other things with it.
|
|
|
|
|
I have a .Net app that uses access as a database and I use the following connection string with no problems. "Provider=Microsoft.Jet.OLEDB.4.0; Data Source=c:\mydatabase.mdb;Jet OLEDB:Database Password=password;"
You could also check out http://www.connectionstrings.com/access[^].
|
|
|
|
|
The problem is in the Add Connection wizard, not the connection string. The same string that yields the completely incomprehensible error message when used with the wizard works perfectly when hand-coded in the app. I'll stick with the old fashioned way of doing connections from now on.
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
|
|
|
|
|
Just came across this post on the VB Developer Center.
Add Connection Wizard Fails[^]
It sounds like the installation of the Access data provider is a bit dodgy.
They suggest the following, and it apparently works a treet.
1) Run regedit.exe;
2) Browse to the location "HKEY_CLASSES_ROOT\CLSID\{F9AE8980-7E52-11d0-8964-00C04FD611D7}" in the tree;
3) If there is a child node in the tree called "ProgID", then you are experiencing a different problem.
Otherwise, follow these steps to modify the registry:
1) Right click the node and select "New > Key";
2) Enter "ProgID" as the name;
3) Go to the main window and double click "(Default)";
4) Enter the value "MSIDXS.1";
Now if you run Visual Studio, it should be working.
Hope this helps.
|
|
|
|
|
Now this is interesting...
I have Visual Studio 2008 Express installed at work, and the registry settings are already exactly what you've described. It works perfectly, using the same database I'm trying to connect to at home.
What's odd is that, my home installation is VS 2008 Standard, and the connection wizard dialog box is entirely different! No Browse button, to start with, and of course I never get past that point to see the rest.
I'll check these registry settings as soon as I get home; this might just do the trick!
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
|
|
|
|
|
That worked a treat!
What an obscure fix for a non-obvious problem! Even worse, this source came from a VS2005 post; why is it still a problem in VS2008?
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
|
|
|
|
|
|
Hello,
does anyone know what is Enumeration in Sqlserver 2005,2008?
what is the advantages and how I can use it? when do I need to implement enumeration?
thanks
|
|
|
|
|
Try doing some research, the question is too large for a simple forum post. Get some idea what you want to know and then ask a more specific question research center[^]
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I don't think databases have enumerations, but you can have a translation table and use referential integrity.
|
|
|
|
|
Hi,
I would like to implement Stored procedure naming conventions on my databases?
I don't want to mess up with developers for this. Is there any way with which my server automatically check
whether the request coming for creation of stored procedure following naming conventions or not??
and if not then it pass error message to developer.
Regards,
Aman
|
|
|
|
|
Try this
create a database[schema] level trigger for CREATE in your database.
go through this for more info.....
Data Base Level Triggers[^]
Cheers..
Rajesh B --> A Poor Workman Blames His Tools <--
|
|
|
|
|
Does SQL Server support database level triggers?
Just realised that the OP doesn't say he is using SQL Server, but I guess the point is, not all databases support database or schema-level triggers.
|
|
|
|
|
David Skelly wrote: Does SQL Server support database level triggers?
Yes - Sqlserver supports the Schema Level Triggers.
Sql Server Schema level triggers syntex/examples[^]
David Skelly wrote: Just realised that the OP doesn't say he is using SQL Server, but I guess the point is, not all databases support database or schema-level triggers.
your right.., but popular database like Oracle, Sqlserver , Mysql .. etc supports Schema Level Triggers . and if you see the OP requirement is such complex/hard to do in the small databases.
Rajesh B --> A Poor Workman Blames His Tools <--
|
|
|
|
|
First, have a policy; make sure everyone has a copy and has read it. They don't need to agree with it, only agree to comply with it.
Second, be sure your policy states that stored procedure names do not begin with sp_.
Third, try the honor system, and see if you need to take further steps.
Fourth, fire any offenders.
Fifth, do as Rajesh said.
Sixth, abandon using stored procedures, they are nothing but trouble.
|
|
|
|
|
PIEBALDconsult wrote: Sixth, abandon using stored procedures, they are nothing but trouble.
That may be your opinion, but many large companies (certainly most financial institutions) insist on them for ease of deployment - if your sql is in your code (dll or whatever) and you have thousands of users worldwide, changes are far more complex than a single stored proc change (even if it does get replicated).
Bob
Ashfield Consultants Ltd
|
|
|
|
|
Hi All,
I have developed an accounting application in vb6 with mssql 7 as backend.
with the passage of time microsoft developed a lot and recently launched VS2010 and MSsql 2010.
Being a developer i updated myself up to VS2008 and Mssql 2008. Currently i am working in Vs2008 and Mssql 2008 express. Upto Mssql 2005 there was no problem between me and my clients. but now as i have upgraded my all systems to mssql express 2008 i am facing problems as some of my client have xp sp2 and mssql 2008 studio does not work with xp sp2.
whenever i tried to install to mssql 2008 studio on xp sp2 it required win powershell which only support on xp sp3. as result i am unable to resotre database to mssql 2005 developed in mssql 2008 express.
kindly suggest me the solution.
Thanks
rmshah
Developer
|
|
|
|
|
Script out your database and recreate it in SQL 2005 by running the script. Then import the data.
|
|
|
|
|
hi iam using sql server 2000
in my table orders the fields are
companyid int
voucherdate smalldate
description nvarchar(50)
the problem is when i say select * from orders ; it is displaying orders like this
1 1/21/2010 1234orderscomleted
2 2/2/2010 67012requireurgent
but i want to display in this format the number with paranthesis and the text
1 1/21/2010 (1234)orderscomleted
2 2/2/2010 (67012)requireurgent
can you give example which helps me
|
|
|
|
|
You can do that in programming language like c# or vb.net but
I think it is not possible using SQL.
Jinal Desai
|
|
|
|
|
By the look of your table design, the numbers and text are simply joined in the field "description". This means it will display exactly as the user has input it!! The easiest way would be for your users to input the data in the format you are after, or change your table design so that the number is stored in its own field, then you could simply select the number and append it into some parentheses!
eg: select companyid, voucherdate, '(' + ordernumber + ')' as FormattedNumber, description from orders
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
