Search results for query: *

i dont think there is a size problem -- i have some pretty big code modules. there could be a number of other reasons, one being a error in the module you're compiling. also, have you upgraded to the newest service pack? i found that for my laptop, i need sp3, but i dont need sp3 for my desktop...

i think you should make the array a global declared in the main code module. if you make the array local to the routine that you are assigning the values to the array will not survive when you exit the routine that logs the keystrokes. the following should help the array declare in the master...

on the flex grid, are you using the textarray feature to load data into each cell? msflexgrid.textarray(cell)=sbuildstring, where cell is an integer, starting with zero as the upper left cell, moving left to right, top to bottom. you can calculate the cell address, and along with the resize col...

is the common dialog control located on the same form as the ms flexgrid? if so, farm out the commondialog to a seperate form and that should take care of the problem. this is about the physical location of the control.

your best bet is to use the textarray feature of the flex grid. this will not only update the grid, but also the display. sometimes, its best to buffer the grid, if possible, so that you dont constantly update the grid until you want to , after updating your buffer. the textarray feature takes a...

some of those api calls work with handles, and some work with task id's. this complicates matters greatly. you'll have to check out setwindowpos and bringwindowtotop along with openprocess to work with window handles. if you try to send messages via the windows api message system, you'll run...

you'll probably have to access a system timer through the win api. the shortest interval in vb is approx 1 ms.

looks as though those embedded blanks are whats causing the problems. i had difficulty with the shell statement and decided to use string variables containing the path and switches and whatever else got thrown in there. also, be sure , if you use strings, to use the + operator when adding the...

try var=instr(str,1,"\") -- this finds where the \ is, and then use mystr=right(str,len(str)-var), where mystr is the result string.

did you make the header row and col fixed? this prevents user from changing these values. use the fixed rows and fixed cols property.

maybe try to assign the fields of the db to string variables first, then assign the string variables to the rtb. since you have embedded formatting assigned to the rtb from the db, you need to strip the formatting out.

another way is to set the controls allow col resize property so that you can resize the col during runtime. this way, you can set the width at startup, but allow the user to resize during runtime. this makes the flex grid not truncate.

flex grids allow you to do that

sorry -- you'll get the error. i ran into the same problem when printing from within the program.