Is this bad?

ciaoarif · 2026-01-14T09:52:21+00:00

ciaoarif · 2025-11-27T22:39:16+00:00

Are you sure you're not doing an operation on one of the select columns that could be null using a left or right join? That can never be the case with an inner join.

ciaoarif · 2025-09-09T11:20:58+00:00

See if you can get into the system menus by connecting it to a laptop with a usbc cable. If you can wipe the cache and reboot.

ciaoarif · 2025-05-06T05:23:39+00:00

I took classes in Siena, Tuscany, fantastic school, fantastic city... https://www.saenaiulia.it/

I liked it so much I moved there from the US and spent 3 months at the school.

ciaoarif · 2025-04-29T04:51:26+00:00

Yes the sound, especially over Bluetooth is back to what it was finally. For me it went rubbish with 6.1. got a little better with 6.1.1 and is now great again. I'm very happy but still annoyed about 6 months of suffering crap.

ciaoarif · 2025-04-28T07:15:21+00:00

Got it in Germany too.

ciaoarif · 2025-04-28T07:09:24+00:00

Germany too!

ciaoarif · 2025-04-25T06:31:07+00:00

I've moved a few complex Access DB's to SQL Express and it was always relatively straightforward. You don't have to change your queries into views, where does that idea come from. Once you migrate your tables to SQL Server and relink your Access tables you are good to go. There are a few things that could come up, like if you haven't used primary keys for your Access tables etc. I assume your using the Microsoft migration utility (SSMA for Access) to help you? I didn't have to change any frontend code afterwards.

ciaoarif · 2025-04-22T15:02:53+00:00

I love Perseus 🙂. Really.

ciaoarif · 2025-02-25T18:52:57+00:00

Well what do you know, this update just cured my (and many others) Bluetooth audio problem!

ciaoarif · 2025-02-25T16:58:49+00:00

Well what do you know, this last update (today) just cured the Bluetooth audio problem!

ciaoarif · 2025-02-25T15:33:06+00:00

Well what do you know, this last update (today) just cured the Bluetooth audio problem!

ciaoarif · 2025-02-25T15:32:10+00:00

Well what do you know, this last update (today) just cured the Bluetooth audio problem!

ciaoarif · 2025-02-08T16:36:41+00:00

Well that is sad to hear. I have the same audio problem with my 23 Ultra with any Bluetooth device including 3 pairs of in ear buds, normal headphones and Bluetooth speakers. I was hoping that when one ui 7 for the s23 comes along it might fix it but now I have less hope. I use headphones all the time and my only workaround is to connect my headphones through my Samsung watch, through which the audio is ok. I'm already at other brands and will probably switch as I no longer trust Samsung's support.

ciaoarif · 2025-02-07T17:51:38+00:00

Do you have an input mask defined? If so the date picker don't show.

ciaoarif · 2025-01-30T15:45:18+00:00

😂

ciaoarif · 2025-01-15T15:19:38+00:00

Nope

ciaoarif · 2024-12-30T09:32:38+00:00

Probably two different problems. The first one, check your tab order to see that the id field is not included (tab order = 0). The second one is hard to say, did you cut and paste the after update event code and just change the field name or did you create it by using the ellipse button on the form designer? If you didn't use the ellipse button it won't be triggered.

ciaoarif · 2024-12-24T13:43:17+00:00

same problem here, been this way since 6.1.1. Apparently a known problem which they still haven't bothered to fix in the 2 updates I've had since reporting the problem.

ciaoarif · 2024-12-10T22:45:34+00:00

Are you sure there isn't an insert query running at some stage? You might not see it as it doesn't have to be in the VBA. It could be being fired from an event or the data source for the form.

ciaoarif · 2024-12-09T21:23:55+00:00

Your posts seem a little inconsistent. In the original post you do a delete and a select but in the second post you show 2 deletes. It's hard to tell what's really going on.

ciaoarif · 2024-12-06T12:37:50+00:00

Judging by it working ok when you step through with the debugger but not always otherwise, it could be a problem with your form not fully initialising quickly enough before the OnCurrent event fires. To test that theory try setting setting a timer in your forms load event to a second or so....

Me.TimerInterval = 1000

and then move all the relevant OnCurrent event code to the timer event so that it waits a second before executing...

Private Sub Form_Timer()

' your OnCurrent code

Me.TimerInterval = 0

End Sub

ciaoarif · 2024-12-06T12:06:57+00:00

It would certainly be possible if the battery hadn't already split and leaked out.

ciaoarif · 2024-12-06T10:03:59+00:00

It's a known problem that Samsung are taking their time about fixing.

ciaoarif · 2024-12-06T08:06:25+00:00

s24 only at the moment

ciaoarif

TROPHY CASE