Goto to Project Properties->ConfigurationProperties->build, check the Register for Com Interop checkbox. This creates a COM interop you can use, add the refernecy myclasses.tlb into your vb6 project
Heres an article on MSDN about creating a custom regex validated textbox
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwinforms/html/custcntrlsamp1.asp
You should find that answers your questions.
You could get the first 100 characters and append '...' to the end, or to make it neater get the first space after the 100th char and do it then so that you get a whole word. That way you get a decent amount of control over the amount of text which is displayed.
It looks like everything worked OK, the test file would contain error messages if it hadnt. The relationships would have been created already if you chose to include them in the SQL sript generated from the exisitng database. If you didnt, recreate the SQL script and check the relationships, and...
I am sure it (SP2) doesnt block select *, this is a key part of the sql language and does have many uses, especially in rapid application development when data changes can be quite frequent.
Backwards cannot be done in ADO.net without the creation of an offline dataset - creating a datareader is easy for forward-only reads.
You will need to create a dataadapter, and use it to fill a dataset which you can then navigate freely. If you have problems doing this, post back and i will help
In IIS 6.0 you need to specifically set the applications which are allowed to serve web pages. Try adding the PGP.exe to the Web Service Extensions tree in IIS on the server and set it to 'Allow'
If this doesnt solve the problem, post back.
Hi
This could be down to PHP not being correctly installed on the web server. What version of IIS are you running, also what error is being returned (404, 500 etc)
Thanks
It will if you choose to script those with the database.
Right click on DB in enterprise manager
All tasks > Generate SQL Script
Click SHow All
Check Script all objects
That will include views, stored procs, tables, functions, etc, etc
I would generate the SQL script as text and once MSDE has been installed on the other computer, run the script using oSQL
For example
osql /S (local) /E /i createappdata.sql /o createappdata.txt
What this means
/S (local) - use the server on the local machine
/E - integrated windows...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.