Search results

I presume your code needs to test whether today is Friday first. I think you are adding 8 less today's day count, so you are always going to return a future date, as the dateadd evaluation is bound to find a date in the future.

Clearly you don't have every error handled because the problem you described is the result of an unhandled error. The other issue with error handling is deciding how you can continue and recover from the error. Sometimes you can just "on error resume next", but often you need to really...

I think there must be benefits for sysadmins if users run system wide apps through terminal services, rather than their own PC. It must be easier to enforce and maintain group policies if all users use the same single login script, and all run the same version of Excel, Access and so on.

There's a numeric value for the setting. I have used it from time to time, but more often as a read value, I think.

I am not sure if this has been touched on, but often spreadsheets aren't designed in the same way as access tables. You may not really need 72 different text boxes on your form. You may need just 3 text boxes on your form, with a continuous form to show 24 rows of data.

@iamchemist I think there is a bit of a "duck test". I tried to add a link to a "duck test", but the short cut was longer than I wanted. Anyway. If it walks like a duck, and talks like a duck, it most likely is a duck. You are describing a situation exactly like one that is caused by the...

Personally, I think I would have two different forms, rather than try to manipulate one form to do different things. It must be easier to do it that way, especially if you are learning Access.

I would have thought it was simpler than trying to dynamically change a query at run time personally. It's much easier to test as well. .

You could change the query to add a clause that switches the optional items on or off, depending. Then you wouldn't need to change the query. Just set a public Boolean variable to say yes/no to include or suppress certain rows.

I forget which way round it is offhand, but the colour value is effectively Rx256^2+Gx256+B The RGB values might be evaluated the other way round. When R,G and B are values in the range 0 to 255

You might be better not reading the new index value until after the record has been saved, whether using Access or SQL server. One problem with an early read is resolving issues with intact sequences if you delete a record after using an auto number value. So one alternative is to not rely...

To do it with strings, you need to get the strings to a standard length, which means storing leading zeros. So if your numbers are 4,2 you need to store 0145-02, not 145-2 or even 0145-2. Alternatively, use 2 fields, so the 145 is in one field, and 2 is in another, and then numerical sorts...

I would imagine either the order price in the order details table is blank, (maybe this wasn't in place at the time of some older orders), or the code to read the saved order price is incorrect.

I think it's a matter of blending your knowledge and experience with the AI results. If the AI helps you solve a problem so much the better. As you say, AI has helped you, which isn't the same as saying AI has replaced you. Hopefully we don't all get replaced by AI. :D

The space for a form control doesn't have to be wide enough to show the whole path. It will still work the same however wide. You can also press shift+F2 to zoom any control (The current control) to see the entire contents. Might there be multiple disk files per record?

I don't really understand your last statement. However I always create a persistent connection at the earliest opportunity. If your speed degrades by adding a second user, then on the face of it, the absence of a persistent connection is the cause. Databases are multi user by design. Even if...

Despite knowing it will happen at inopportune moments, I still get caught by that one from time time to time. :D

This definitely sounds like a persistent connection issue to me, as mentioned by @CJ_London Did you write the database? Have you added code to maintain a persistent connection? If not, that's the first place to look.

The easy way is just to allow certain users/user groups to open a form or not. The hard way, needing painstaking coding, is to allow users to do different things on the same form. Pat just showed a way to use the "tag" property, but then you have do decide all the special actions to want to...

Even that distinction may be difficult. Setting a form to "allowed edits = false" may prevent you changing values in combo boxes for instance, and I'm sure that's not what you want.