Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Flexibility run-time error 380-Invalid Property Value

Status
Not open for further replies.

jdaub

IS-IT--Management
Jul 12, 2002
10
US
I have a very simple Flex script that pops open a window displaying some customer-specific info from the Order Entry screen in Macola (7.5.103f), when the ShipVia field loses focus. I am running this on Win98 machines. It runs fine on most machines, but on two (so far) I get this run-time error 380-Invalid Property Value message upon loading the Order Entry app, and then again once the screen appears, and whenever you do anything within this screen.

Of course, the machine I really need the mod to run on is one of the two misbehaving machines.

I have tried everything I can think of, playing with properties, using VB controls vs Macola controls, killing all nonessential activities on the machine in question, video settings, reinstalling Macola/Pervisive clients, ect., etc.,etc.

I am hoping that this is something simple that others have run into before. I would greatly appreciate any help. I do not pretend to be a programmer, although I have been dabbling in VB for a while (just enough to get the job done). Below are the pertinent code snippets, although I suspect that this has something to do with the environment of these particular machines are it runs on others just fine.

MACFORM Code:

Option Explicit
Dim rst As New ERSRecSet
Dim strSQL As String
Dim strConnect As String

Private Sub ShipVia_LoseFocus(AllowLoseFocus As Boolean)
strConnect = "DRIVER={Macola 32-BIT Btrieve (*.dta)};DFE=BTR;" & _
"AS=4096;DB=" & macForm.ConnInfo.BtrPath
rst.ConnectString = strConnect
strSQL = "Select Cus_Type_Cd from ARCUSFIL_SQL where cus_no = '" & CStr(Format(macForm.CustNo.Text, "000000000000")) & "'"
rst.Open (strSQL)
If (Left(rst("Cus_Type_Cd"), 2) = "ID" Or Left(rst("Cus_Type_Cd"), 2) = "DM") Then
frmCustType.Show
rst.Close
Set rst = Nothing
End If
End Sub
Option Explicit
Dim rst As New ERSRecSet
Dim strSQL As String
Dim strConnect As String
Dim strSalesLastYear As String
Dim strDateLastChanged As String


USERFORM Code:

Private Sub UserForm_Initialize()
strConnect = "DRIVER={Macola 32-BIT Btrieve (*.dta)};DFE=BTR;" & _
"AS=4096;DB=" & macForm.ConnInfo.BtrPath
rst.ConnectString = strConnect
strSQL = "Select Cus_Type_Cd, User_Def_Fld_3 from ARCUSFIL_SQL where cus_no = '" & CStr(Format(macForm.CustNo.Text, "000000000000")) & "'"
rst.Open (strSQL)
strSalesLastYear = Left(rst("User_Def_Fld_3"), 12)
strDateLastChanged = Mid(rst("User_Def_Fld_3"), 16, 8)
txtCusType.Text = rst("Cus_Type_Cd")
txtSalesLastYear.Text = strSalesLastYear
txtDateLastChanged.Text = strDateLastChanged
rst.Close
Set rst = Nothing

End Sub

Thanks,

Jeff
I/T Director
jdaub@walkermagnet.com
 
It doesn't get that far. The event that lauches the code is the Ship_via lose_focus event from the order entry screen, but the error shows up while the order entry screen is loading, before you key in any data.
 
More info- The order entry screen does eventually load, but every time that you touch a key or click the mouse the 380 error message pops up again. It is impossible to use the VBA environment debugging tools because of this.

Jeff
 
I don't think you are going to have a simple answer to this. Invalid property values that cannot be traced back to a line of VB code is going to be the result of bugs in Macola. It is either passing or receiving some value to or from the operating system that is invalid.

First, you have to determine if it is due to some local situation on the machine. Check the follwing.

When you log in to the machines that work, are you using the same login that you use on the machine that doesn't work? If the error happens on any machine that you use a particular login on, you have a corrupted screen set or project for that user.

If the problem is not connected to the login, then you have a local machine problem. Check to make sure the machine has the latest Win 98 service packs. After that, try to determinw what the two machines have in common, and what is different about them from the machines that work.




 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top