Search results for query: *

I am doing a pretty vanilla connection to a SQL Server. (The code follows) String strSQL = ""; //get the connection try { strSQL = "data source=" + txtServer + ";initial catalog=" + strDatabase + ";persist security info=False;user id=sa;packet...

Geoff, This can sometimes happen if you have installed a visual basic application on your development machine. What happens is that the activeX controls lose their development license and can't be used in VB anymore. Also this can happen if a rogue application overwrites your comctl32.dll with...

dvannoy, I recommend STRONGLY against using the above code as it can introduce a horrible security risk with SQL Server, please imagine what would happen if somone typed in "sp_execute(truncate table Cust)" command into your textbox, or worse! SQL Server will let you pass through...

Please research the Validate event. It is the proper event to use for handling lost focus types of problems... Microsoft introduced this event to solve EXACTLY the problems you are discussing...

We have done alot of this type of thing, I have found BY FAR that easiest solution is to just go to VB Extras and buy a component to do it for you ;-) -recurse

Try the following: dim cn as new adodb.Connection dim rs as adodb.recordset cn.open "Provider=SQLOLEDB.1;Persist Security info=True;User ID=genericuser;Password=;Initial Catalog=YOUR_DATABASE_NAME;Data Source=TESTFUSION1" set rs = cn.execute("select * from tblPart");

sonper, Yes, you can use record locking to implement the behavior that you are describing, but locking techniques are wildly different dependg on the backend you are using. If you are using a SQL Server backend you can use a WITH locking hint on your sql query which will lock the records at...

Just a guess... have you tried having a batch file (that you are shelling out to) first do a NET LOGON <username> <password> as Administrator, then call the install? Hope that works..

Craig, You have the right idea but you are going about it a little backwards. There is no way intercept the description of an enum at runtime, enums are specifically meant as a convience for developers to allow parameters and other data to be descriptive rather than numeric hard-coded values...

This is the infamous &quot;binary compatibility&quot; myth. The problem you are having is caused by having a reference to a newer/different version of ADO. Make sure that in your project->references check the version of ADO you have a reference to. Then do as chiph recommended and install...