Search results

I wouldn't worry about a user entering 21 items. Could you check on starting whether the table is now "full", ie >=20 items, and don't let them add new ones at that point.

I don't know if this is the same. I have strings to be processed, and include replace tags surrounded by curly braces. {Employee_name} I explicitly check for all pre-defined tags and replace them as appropriate. Is that relevant for what you are doing?

It would be interesting to know what fields you have. Given that a payslip once produced would never be altered I would be inclined to include some cumulative values in the payslip record, such as "total tax paid in this employment",which is re-evaluated as you produce each pay slip. It's a...

If they are many to many (i assume that is what is meant by N:M, then that cannot be represented in a relational database, and has to be replaced with a junction table, to yield 2 x 1:N relationships. For example, a customer cannot be directly related to ordered items. You have to include a...

I doubt it's crackable, especially as you have such a small amount of encrypted data. When you created an mdw file, access/ms did give careful and explicit warnings regarding the password, and it's security. Perhaps you weren't involved personally at the time. You might try...

I assumed it was me just not understanding, but maybe not.

If you do it the other way. ... Find items with no difference, then everything else is a difference.

Don't forget that Access makes lots of things very easy. Data binding, data updates, continuous forms. It will be enormously difficult to programme that all in. I keep trying it out, and the data binding/continuous forms stuff just seems so difficult to achieve. If I could get that working, I...

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...