Recent content by neilharris

Is there any reason why you wish to parameterise a simple statement like that. Surely it would be much easier to simply set up the complete strSQL in the first place. I.e.: strSQL = "select * from my_table where add_user_id = 'BillLumbergh' and type_id in (1,2,3)" Set cnn =...

What is the actual statement it isn't executing?

In the files setup dialog if you select the application folder entry then you get its properties. There is a property called default location which defaults to: [ProgramFilesFolder][Manufacturer]\[ProductName] If you change this to: [ProgramFilesFolder][ProductName] It should do the trick.

You could overload the interfaces that are used to manage the panel collection to only allow operations on other panels.

You may be correct in which case you would need to set the commandtype properties on each of the other commands. The default is CommandType.Text which obviousley won't work calling a stored procedure.

Or if you really need to pass the variables in simply overload the Sub New in the form you are creating to accept the necessary variables.

write a function that returns the necessary string in the event of a null. EG: Function NullToString(Val,RetVal) If Isnull(Val) Then NullToString=RetVal Else NullToString=Val End If End Function Then you would call it for each field, eg: tempforcecode = NullToString(RS("force_code"),"-")

It looks like you haven't created any sort of SQL statement for the update command to use, which is why it is complaining that it cannot find any of the SQL reserved words that it is expecting.

If the variables are declared within a module as Public then they will be available to the next form that opens anyway. Why would you need to pass them in to it?

Thats seems fine, although I would suggest you write a stored procedure that takes all of the data writes the record and returns you the id. That way it is all in one transaction and you won't run the risk of getting the wrong ID when two are added simultaneously.

Yes it is perfectly possible however it may be quite difficult to implement complicated formatting changes. Once ASPTear has retrieved the page it is simply a string object. Therefore you can use any string manipulation functions you wish to, in essence, rewrite the html before it is written to...

Your querystring variable is named incorrectly, it should read: Response.Write "<a href=""CJ_Last_Week_by_Manager_D.asp?Page=" Response.Write Current_Page + 1 Response.Write "&ManagerName=" Response.Write Mgr

You have an unnecessary @ sign in that, it should read like this: Response.Write "<a href=""CJ_Dates_by_All_AD.asp?Page=" Response.Write Current_Page + 1 Response.Write "&DateFrom=" Response.Write Date_from...

You may find that widthArea = Replace(widthArea, chr(13),"<br>") works better, as I think that the textarea only puts a carriage return and not a linefeed as well.

the problem lies with this code: If Current_Page < Page_Count Then Response.Write "<a href=""CJ_Dates_by_All_AD.asp?Page=" Response.Write Current_Page + 1 the querystring only passes through a page number which means on page 2 onwards: set Date_From = request("DateFrom") set...