Um why do you want to 'see' the scroll bar if you are not using it? You know it is still there so what is the problem? My Mrs styles herself Annie O'Luddite. You would probably get on well with her. :laugh:

Yup, some of us have been in this business over 30 years, including me, and some of us have moved with the times. Frankly I would not still wish to be using ANSI Basic 1.0 or MASM 1.0 Sounds like with all the moans about "Start" you should use Classic Shell, or is that a tad too modern for you? ;P

I have W10 on PC, notebook and tablet. No unplanned reboots, no crashes, no problems. Maybe I am just lucky! ;P

I upgraded to Win 10 and have never had a problem with it. Maybe because I don't play any games - only use it for development and browsing. Sure it needs a bit of tweaking to make it behave but with Classic Shell installed because I don't like tiles basically all the rest is exactly the same under the hood, apart from very minor differences, to XP. My laptop is Win 10 now and also my tablet so I guess I have embraced Windows 10!

A somewhat misplaced attempt at humour I feel.

It's OK I understand what you were saying, but I was thinking that maybe people ding the job had come across the problem and fixed it or got a workaround. Unfortunately there is nothing much about it on that site. The problem gets a mention. Apparently it appeared in 2.6 and has not been fixed satisfactorily as far as I can tell. The forum is a bit 'thin' to say the least. In the end, because the code has to address .NET 4.0 I simply re-compiled version 2.5 to target the .NET 4.0 framework. Since the problem does not exist in 2.5 I am happy and I am not concerned about the additions in later versions that i will not have by using 2.5. At least if someone else experiences the problem our discussion is here to give them a pointer. Thanks for your input. :thumbsup:

It is implemented in Visual Basic therefore the question is legitimate. I will ask in the suggested forum however although I have already searched that and found nothing specific.

If you have access to Visual Studio 2005 you can do it in two steps. VS2005 has a converter from VB6 to VB2005, and 2010 has a converter from 2005. Whilst that may be helpful if it is available to you as an option you still need to understand VB.NET as the converter will leave many things that have to be tweaked by hand.

A docking pane is set to AutoHidePortion and permitted docking is DockLeft with AllowEndUserDocking = False The design width of the form is 200px and the initialisation command is .Show(dockPanel, DockState.DockLeftAutoHide) Despite the fact that AutoHidePortion is > 1 the pane is showing at around 315px = 1/4 the form width. I have just moved from DPS ver 2.5 to ver 2.8 and in ver 2.5 this behaviour is not apparent and the form (pane) displays at the required size. I an using VB 2010. Does anyone have any further information on this, workarounds or fixes? I can't seem to find anything specific on the web, or in Code Project. Thanks.

Thanks for your input. Yes I am adding some filtering now. I just needed to get the thing working first.

Ah yes. My bad

SELECT quakeid, latitude, longitude, (6371 * acos(cos(radians(37)) * cos(radians(latitude)) * cos(radians(longitude) - radians(-122)) + sin(radians(37)) * sin(radians(latitude))))
FROM tblUSGSData
GROUP BY quakeid, latitude, longitude
HAVING (6371 * acos(cos(radians(37)) * cos(radians(latitude)) * cos(radians(longitude) - radians(-122)) + sin(radians(37)) * sin(radians(latitude)))) <= 50

works - at least does not produce an error. Not sure about the working bit but that is another story. Many thanks.

I am sure I am overlooking something very simple but I can't see it. I have a database of locations with latitudes and longitudes. I need to be able to query for locations that fall within a given radius from a lat/lon point The code I am intending to use is: (Showing fixed centre 38,-118 in this version)

SELECT quakeid, (6371 * acos(cos(radians(38)) * cos(radians(latitude)) * cos(radians(longitude) - radians(-118)) + sin(radians(38)) * sin(radians(latitude)))) AS [dkm]
FROM tblUSGSData

(Derived from Creating a store locator[^]) This works fine and returns just over half a million entries. My problem is that as soon as I add

HAVING [dkm] <= 50

or

WHERE [dkm] <= 50

I get the message Msg 207, Level 16, State 1, Line 3 Invalid column name 'dkm'. I obviously have not got my SQL glasses on today as I can't seem to resolve this. Can any one make (polite) suggestions?

Thanks again. Just one final question, does this also apply to Forms in the project, i.e. if a form is not referenced in code because of the compiler directives it does not get assembled into the exe?

Many thanks indeed for that. I did not realise that the reference would not be created if the DLL was not used. Two setups is not a problem. Gave you a 5 for that one! :)

It is a long time since I used Access and VB6 but as I recall the dates in the mdb file are always in American format (mm-dd-yyyy). What I don't understand is how 28 Jan 08 remains untouched! Possibly the problem is that 28 Jan 08 does not have an American equivalent so is forced to what happens to be the correct format. You should set something up to specifically format your dates as you want to see them rather than depend on the built in stuff.

That is totally weird! It has always done whatever is set on the menu for me whether to use build on the menu, or run or right click and build on the solution in solution explorer. Would this be an Express thing perhaps? I have never used the Express versions and have always used the configuration manager to set things up.

I hope this explains my problem. I have two versions of a program, not basically very different, a 'standard' and a 'pro' version that are controlled using compiler directives. My problem is that the 'standard' version uses one DLL and the 'pro' version uses a different one completely, by a different vendor. Basically zedgraph and spreadsheetgear respectively. I don't particularly want to send both to both versions of the program but I can't seem to see a method using compiler directives (?) of having one reference for one and the different reference for the other. This also extends to the setup and deployment program as that also seems to only relate back to the project assemblies as far as debug/release are concerned and does not allow for different file sets, or have I missed something?

Pretty much what I was thinking. Thanks for you help.

Thanks for responding. I understand the differences between char and varchar but what I am trying to find out is what type I should give a parameter. I have a char(1) field that accepts data in a routine. In an SQL Server stored procedure I would give this the SqlDBType.Char type. There seems to be no equivalent in MySQL so my question was do I just use MySqlDBType.VarChar?

Sorry what assumption am I making? There is only one database There is only one server which is the machine the program, VS and data are on. The data in VS is not committed because it is already in the database. I am reading it not writing it. Thanks for your time on this one :) but I have decided to change over to MySql. I can't be doing with the vagaries of Microsoft.