Search results

I'm not sure about that, and in any case, I would probably avoid 'did you use[d] to' altogether in favour of something that feels less awkward ('did you once own...', perhaps)

You need Docmd.OpenForm, I think. And probably Select Case instead of a series of sequential IFs And are the forms really so different from each other? If not, I would suggest designing a single form and locking, hiding or disabling the components and functions that the lower-rank users...

It's meant to be: used to. The reason use to is common is that in spoken form, the D sound often gets dropped or merged into the T sound that follows it - and people hearing this (especially kids) acquire the habit of writing it as it sounds. Same sort of thing with 'could have' - because...

I agree. Restricting access to the BE by Group Policy is a great way to help to secure your application. Definitely don't just bung it in a 'common' folder - some eejit will delete or damage it.

Could count consist of any number (including really large ones), or is there an upper limit? If there's an upper limit of, say, 10, you could create another table called (say) 'instances' and populate it as follows: 1 2 2 3 3 3 4 4 4 4 (etc) Then include this table in your query and join it to...

What you need is to get them to make one common location visible to all three offices and put the BE there. Users running the FE will need read/write access to that shared location.

I can't help thinking there might be some other usage of the ? character as a prefix that has meant the query designer can't safely make the assumption that you are in fact typing a string. I don't know that for sure, of course (the only other usage I've seen like that is in some BASIC...

A couple of other things you might need to know about working with dbf tables from Access... 1. Certain versions of dBase have a philosophical disagreement about dBase file header structure - the second byte in the actual file describes the year the file was last updated. Some...

DBF tables allow the explicit definition of the number of decimal places in their structure. One way to get what you want is to first, create (using dBase) a template dbf with exactly the structure you want, then in your VBA, copy the template to a new filename, link the new file as a linked...

Fair enough - that also works. I don't think a composite key would hurt here though, given that it would be based on two entirely synthetic foreign keys (if it was a composite of client account number and some human-readable service code, I would be dead against it)

I don't like composite keys either, but I think this might be a case where they are worth having. If ClientID + ServiceID are used to form the PK, it will prevent any client being assigned the same service twice. I might still have an autonumber field just for record identity - so I can point...

What version of Access is installed on the machines of the people that will use the database?

I'm going to give it a try. I've got 8.10 on my dual-boot home PC at the mo.

If the tables are growing to the extent that they all need separate databases, isn't that an indication that they might grow further so that some of them may individually become too large? If it's important enough to be planning by splitting them all out, I think it's important enough to...

1. Sounds interesting, as far as I am able to understand what you're saying. 2. No objection - I have sidebar ads on my own site (although they always come below content, and are kept separate), and I recognise the importance of ad revenue to webmasters. I hope the ads will be sensibly...

I'm not sure that what you want to do can be accomplished without some tricky Windows API programming (that I am not qualified or experienced enough to advise on). But it sounds like maybe Excel just isn't the right tool for the task you're performing. Seems like you need a proper desktop...

You'll need to join the two tables (in your query) by something common such as serial number - then you can calculate the difference between the bought date in one table and the broken date in the other, for corresponding pairs of records.

Do the tables include an identifier by which you can ascertain which product was sold and when that specific product broke? (something like a transaction number, or in the case of multiple line transactions, a transaction number plus item ID?) You need some way of identifying which breakage...

As long as the application is a fairly simple one, I've recently taken to creating it all in one form with a tab control - and instead of having separate little forms, each distinct function of the application has its own tab. That way, you don't have to worry about what happens if they manage...

Driveimage XML http://www.runtime.org/driveimage-xml.htm