Search results

@Gasman, you've got me jealous now. I haven't been diving in almost 10 years and miss it!

In theory, the entire query returned can reside in memory. Table entries by nature are always stored to disk. Your betting money that a disk some place is faster that the computer's memory...

Were this me, I would probably use a sum query on $Medicare and use a control to hold the title. This lets you use the same structure for any title.

I'll third @theDBguy's comment. Main reason is to avoid having each tester see changes made by another users UNLESS this is what is being tested. Think through how an end output, such as a report, will look when multiple users are using the system at the same time. Can be a pain if others are...

I'd first I'd include NewName in your declarations. Then I'd make sure what is in OldName and NewName are what you expect.

If these are for internal use only, you can write a routine that outputs them to HTML, thus allowing a browser to worry about viewing them and printing them. Issue that will pop up is, even if you can get the image or document to show, your still using the print size (paper, orientation, and...

When you build SqlStr2, your FROM is the same table as you are inserting into. I'd suggest making a query that returns ONLY those fields from tblProducts (qryProducts maybe) and trying with the query as your FROM.

Also makes sense when someone move from one known location to another known location. Update link rather than enter entire new address. Example is when a child moves from mom's place to dad's. OP also has "Activities", so would make sense to have the option if their "Activities" are not always...

Special note on address tables. I've always found it more useful to have a linking or junction table that relates an individual or organization to an address. This allows me to also have a "FromDate" and "ThruDate". This way when James Jones Jr. moves out, you'll track that he USED to live with...

Normally when I see DMax() used for customer facing numbers it is stored as a "PO" or "Receipt" number rather than "RecordNum". Hence the question as I'd hate to think OP is trying to reinvent fire!

Trick I learned from a realtor; Let vanilla extract thicken a bit so it can be placed on an incandescent lightbulb. Place the thickened extract on a low watt lightbulb and let it dry. Turn on the light the bulb is in and your house will smell like a bakery in a few minutes.

Why are you trying to do this instead of having "RecordNum" be autonumbered? I'd also give it a better name than "RecordNum". DemoTrans_ID may be a better name as it makes it very apparent it is the primary key for the DemoTrans table, the main reason you use an autonumbered field.

But the broken digital clock could always be telling you how long until NOW!

Can you please describe what is going on for the form that would prevent you simply making it required? Without knowing what the scope of your solution needs to be, you'll get a bunch of solutions that won't work for your situation.

@OP, Just to make sure, this is intended to be a single user system that cannot allow two users to work on Parent records at the same time? The " Where MainID is Null;" means if you have more than one person entering entries in tblLineUnitEntries at the same time, who ever trips this code FIRST...

I've uninstalled it... the hard way... and had it reinstall with the following update. Just doesn't make sense to have something like that ALWAYS on the machine though.

Now if Microsoft could realize not all computers need to have a "Game Bar" loaded....

Question for OP, will any of the documents or images take up more than one page?

When linking to excel tables, Access will attempt to identify what type of data you are using in a given column based on the values of the first 20ish rows. Unfortunately this may not be true for all values in that column. This causes major issues with Access. Unless you are using a lot of data...

Do you have a child table to members for their membership/renewal? Were this me, I'd have a child for "Payments" that includes "RenewalDate". You could then run a process based on RenewalDate to insert payments due and have that do the look up based on their age at RenewalDate. This give you a...