Search results

My statement was missing an 'if' 😖 It should have read: I looked at the code just now - it doesn't use proper subclassing (e.g. GetWindowProc() ), so my point was not relevant.

I haven't looked at the Leban's code, but it uses proper subclassing (e.g. GetWindowProc() ) then you can not have the VBA editor open while the code runs. It will always crash Access.

If you have two different versions of SQLServer being served from the same machine then surely you need to assign one to serve on a different port from the other?

There is some old code here on The Access Web but you will probably have to find update versions of the API declarations for 64bit.

No one mentioned a form! :LOL: Time for some new glasses! :geek: (or Ctrl and + to increase the scale of your browser)

Interesting. How many iterations did you require to be able to see a noticeable time difference? Also, did you perform this in VBA? I ask because, IIRC, IIf() works differently in a query than in VBA. In VBA I think both the True and False parts are evaluated, even if the condition is True...

I think your SQL is wrong. Try instead: Public Sub UpdateFieldSizeToShort(tableName As String) With CurrentDb .Execute "ALTER TABLE " & tableName & " ALTER COLUMN Umsatztext VARCHAR(255)", dbFailOnError End With End Sub

It's very hard to miss you, @theBigGreenguy :ROFLMAO:

Can we dial back a second @Gasman - how did you do the Save/Load as/from text? Like: Application.SaveAsText acForm, "frmName", "C:\path\to\file.txt" ' and Application.LoadFromText acForm, "frmName", "C:\path\to\file.txt" ?

Is that a question?

Did you delete the existing form before importing from text?

Probably more like: DoCmd.OpenForm "frmCustomerInvoice", Where:="1 = 0"

Change the form's RecordSource to: SELECT m.*, c.riskSLcode FROM TMain m INNER JOIN FriskSL c ON m.RiskCode = c.riskSLid Then set the ControlSource of your textbox to [riskSLcode]

It might also be wise to use a different object variable for looping the .Controls collection in case ctrl is used subsequently in the calling code. Additionally, the +1 will need to be incremented for every control skipped for being TabStop = False or Enabled = False

Choose() is probably a better choice than Switch() if you want to avoid the table option.

There are 25 risk codes - with either Switch() or nested IIf(), my guess is that you are butting up against or beyond the maximum number of arguments.

When you have this many it's easier to create a table for risk codes; then join the table without the need for such an unwieldy expression or VBA function.

Do this. (y) Option Explicit will then be added automatically to all new code modules But you will also need to add it manually to all existing code modules.

Make sure you have Option Explicit declared at the top of every code module (above or below Option Compare Database). This will catch any errors for undefined variables/constants or typos in your code.

Yes. How are you executing your pass-through?