amorosik
Active member
- Local time
- Today, 16:12
- Joined
- Apr 18, 2020
- Messages
- 581
This is truly incredible (at least for me).
Program1.accde becomes program2.accde after some changes to the 'articles' form.
Both program1 and program2 work correctly on the development PC, with Win10 with Access 2013 32bit
Let's move to user PC2, a Win10 pro pc, where only the Access runtime 2013 32bit is installed.
Program1 works correctly on user PC2.
I send program2 to user PC2, and when I open the 'purchases' form on form_load, it throws me an error 2766 and 3146 on Me.Filter and me.FilterOn
Private Sub Form_Load()
Me.Filter = "REGISTRATION_DATE >= #" & dataSQL(Format$(DateAdd("m", -1, Now))) & "# "
Me.FilterOn = True Me.OrderBy = "ID_DOC desc"
Me.OrderByOn = True
End Sub
The dataSQL function reverses the day and month in the dates field
Tables connected via ODBC to a Firebird database server, the REGISTRATION_DATE field is a Timestamp
The database to which program1 and program2 are connected is the same
Note that the 'purchases' form has NOT been changed from program1 to program2; it is identical.
So on PC2, the 'purchases' form is the same between program1 and program2, the data is identical, and the Windows on PC2 is identical.
There should be no reason for program2 not to work while program1 works correctly.
Access options verified and identical between program1 and program2.
I investigated a bit and saw that the problem on program2 is the dates.
On program1, if I enter "REGISTRATION_DATE >= #07/19/2025#" it works correctly.
However, if I do the same thing on program2, it doesn't work;
On program2 I have to enter "REGISTRATION_DATE >= #19/07/2025#"
Note that this problem occurs on different versions of program1, but on the same PC2, and therefore it doesn't work.
It could be a problem with the date/time settings and similar bullshit, or a different ODBC driver version because both program 1 and program 2 are using on pc2 the same DNS.
What could this depend on?
Any advice?
Program1.accde becomes program2.accde after some changes to the 'articles' form.
Both program1 and program2 work correctly on the development PC, with Win10 with Access 2013 32bit
Let's move to user PC2, a Win10 pro pc, where only the Access runtime 2013 32bit is installed.
Program1 works correctly on user PC2.
I send program2 to user PC2, and when I open the 'purchases' form on form_load, it throws me an error 2766 and 3146 on Me.Filter and me.FilterOn
Private Sub Form_Load()
Me.Filter = "REGISTRATION_DATE >= #" & dataSQL(Format$(DateAdd("m", -1, Now))) & "# "
Me.FilterOn = True Me.OrderBy = "ID_DOC desc"
Me.OrderByOn = True
End Sub
The dataSQL function reverses the day and month in the dates field
Tables connected via ODBC to a Firebird database server, the REGISTRATION_DATE field is a Timestamp
The database to which program1 and program2 are connected is the same
Note that the 'purchases' form has NOT been changed from program1 to program2; it is identical.
So on PC2, the 'purchases' form is the same between program1 and program2, the data is identical, and the Windows on PC2 is identical.
There should be no reason for program2 not to work while program1 works correctly.
Access options verified and identical between program1 and program2.
I investigated a bit and saw that the problem on program2 is the dates.
On program1, if I enter "REGISTRATION_DATE >= #07/19/2025#" it works correctly.
However, if I do the same thing on program2, it doesn't work;
On program2 I have to enter "REGISTRATION_DATE >= #19/07/2025#"
Note that this problem occurs on different versions of program1, but on the same PC2, and therefore it doesn't work.
It could be a problem with the date/time settings and similar bullshit, or a different ODBC driver version because both program 1 and program 2 are using on pc2 the same DNS.
What could this depend on?
Any advice?