HMGforum.com

Hola :
tengo implementado en un sistema de facturacion un control browse para busqueda de articulos que es muy eficiente pero ultimamente esta causando este error que causa que se cierre el sistema .

Hello :
I have implemented a system of billing a browse control to search for items that are very efficient but lately is causing this error that causes the system to shut down.

Uso HMG.3.4.2 con su IDE con Windows 7 .

Saludos
Mario Mansilla


Date:26/05/2016 Time: 17:41:18
Error BASE/1132 Error de rango: acceso al array

Called from _BROWSEGETVALUE(1269)
Called from _BROWSEREFRESH(1046)
Called from EVENTS(2393)
Called from REDRAWWINDOW(0)
Called from _REFRESH(4507)
Called from DOMETHOD(9029)
Called from BUSCAR_ARTICULO(3694)
Called from (b)BF_ARTICULO(151)
Called from _DOCONTROLEVENTPROCEDURE(6036)
Called from EVENTS(1815)
Called from DOMESSAGELOOP(0)
Called from _ACTIVATEWINDOW(5699)
Called from BF_ARTICULO(3584)
Called from (b)ALTA_VENTA(131)
Called from _DOCONTROLEVENTPROCEDURE(6036)
Called from EVENTS(2205)
Called from DOMESSAGELOOP(0)
Called from _ACTIVATEWINDOW(5699)
Called from ALTA_VENTA(955)
Called from (b)FACTURA(1180)
Called from _DOCONTROLEVENTPROCEDURE(6036)
Called from EVENTS(1755)
Called from DOMESSAGELOOP(0)
Called from _ACTIVATEWINDOW(5699)
Called from FACTURA(171)
Called from (b)MAIN(119)
Called from _DOCONTROLEVENTPROCEDURE(6036)
Called from EVENTS(1717)
Called from DOMESSAGELOOP(0)
Called from _ACTIVATEWINDOW(5699)
Called from FACTURA(171)
Called from (b)MAIN(119)
Called from _DOCONTROLEVENTPROCEDURE(6036)
Called from EVENTS(1717)
Called from DOMESSAGELOOP(0)
Called from _ACTIVATEWINDOW(5699)
Called from FACTURA(171)
Called from (b)MAIN(119)
Called from _DOCONTROLEVENTPROCEDURE(6036)
Called from EVENTS(1717)
Called from DOMESSAGELOOP(0)
Called from _ACTIVATEWINDOW(5699)
Called from FACTURA(171)
Called from (b)MAIN(119)
Called from _DOCONTROLEVENTPROCEDURE(6036)
Called from EVENTS(1717)
Called from DOMESSAGELOOP(0)
Called from _ACTIVATEWINDOW(5699)
Called from FACTURA(171)
Called from (b)MAIN(119)
Called from _DOCONTROLEVENTPROCEDURE(6036)
Called from EVENTS(1717)
Called from DOMESSAGELOOP(0)
Called from _ACTIVATEWINDOW(5699)
Called from FACTURA(171)
Called from (b)MAIN(119)
Called from _DOCONTROLEVENTPROCEDURE(6036)
Called from EVENTS(1717)
Called from DOMESSAGELOOP(0)
Called from _ACTIVATEWINDOW(5699)
Called from FACTURA(171)
Called from (b)MAIN(119)
Called from _DOCONTROLEVENTPROCEDURE(6036)
Called from EVENTS(1717)
Called from DOMESSAGELOOP(0)
Called from _ACTIVATEWINDOW(5699)
Called from FACTURA(171)
Called from (b)MAIN(119)
Called from _DOCONTROLEVENTPROCEDURE(6036)
Called from EVENTS(1717)
Called from DOMESSAGELOOP(0)
Called from _ACTIVATEWINDOW(5699)
Called from FACTURA(171)
Called from (b)MAIN(119)
Called from _DOCONTROLEVENTPROCEDURE(6036)
Called from EVENTS(1717)
Called from DOMESSAGELOOP(0)
Called from _ACTIVATEWINDOW(5699)
Called from FACTURA(171)
Called from (b)MAIN(119)
Called from _DOCONTROLEVENTPROCEDURE(6036)
Called from EVENTS(1717)
Called from DOMESSAGELOOP(0)
Called from _ACTIVATEWINDOW(5699)
Called from FACTURA(171)
Called from (b)MAIN(119)
Called from _DOCONTROLEVENTPROCEDURE(6036)
Called from EVENTS(1717)
Called from DOMESSAGELOOP(0)
Called from _ACTIVATEWINDOW(5699)
Called from FACTURA(171)
Called from (b)MAIN(119)
Called from _DOCONTROLEVENTPROCEDURE(6036)
Called from EVENTS(1717)
Called from DOMESSAGELOOP(0)
Called from _ACTIVATEWINDOW(5699)
Called from DOMETHOD(8941)
Called from MAIN(61)

Hola Mario:

Podrías postear el código para analizarlo, ya que simplemente con los errores es imposible determinar que lo causa.-
En alguna ocasión me pasó algo parecido con el comando Grid, y la causa era que omití re-filtrar la tabla y en su lugar había refrescado el mismo.- Si el browse está filtrado, procurá repetir el filtrado antes de entrar a una nueva busqueda.-
Cordialmente.
Eduardo

Hola Eduardo :
te posteo la parte del codigo que provoca el error .
Este codigo esta en el Onchange de un Textbox que actualiza el Browse .
Generalmente sucede con los operadores mas rapidos y no lo realiza siempre .

Saludos
Mario Mansilla

*------------------------
Static Procedure Buscar_Articulo
*------------------------

Local ldigito := .T.
Local lBusca := Trim(Form_103.Text_1.Value)

Do Case
Case Form_103.Combo_1.Value = 1
For I = 1 To Len(lBusca)
*--
If !IsDigit(Substr(lBusca,I,1))
ldigito := .F.
Exit
Endif
*--
Next
If lDigito
Arti->(DbSeek(Str(Val(lBusca),13)))
Else
MsgInfo("Debe ingresar valor numerico","Atención")
Form_103.Text_1.Value := Space(20)
Endif
Case Form_103.Combo_1.Value = 2
Arti->(DbSeek(Trim(Form_103.Text_1.Value)))
Endcase

Form_103.Browse_1.Value := Arti->(Recno())
Form_103.Browse_1.Refresh (en esta linea 3694 se provoca el error)

Return

Hola Mario:

Probaste reemplazar el ONCHANGE por ONENTER, con lo cual el BROWSE se actualizará cuando salgas efectivamente del Control TEXTBOX.-
Nada obsta a intentar reindexar la base una vez que salis del TEXTBOX.-
Yo padecí en reiteradas ocasiones este problema con operadores "superspeed", y para evitarlo los obligué a pulsar un botón de confirmación (no es lo más recomendable pero solucioné el problema y se acostumbraron a usarlo).-
El BROWSE lo dejé de usar desde la versión 3.30 y me volqué definitivamente al GRID, y me resultó sustancialmente más veloz ya sea trabajando con tablas o con arrays multidimensionales.-
Lamento no poder serte de mayor ayuda.-
Un abrazo.
Eduardo