Search results

Good morning, Bill. Once the table design is finalized, hopefully with the rules of normalization, and the relationsihips setup, then you need to design a form. The form will handle the entry of your data and any editing, also. The form can have its' recordsource either from table or a query...

Bill, we look at data through forms, in forms we can create records, modify records and delete records, but it is all data. Form forms we can print reports and from queries we can print reports. As for what you showed me think about this: In Table: IDNo Autonumber(Pkey) Compartment - Combo...

Your welcome. Candace is a very talented lady, as you can see. LOL.

First the remote dbase is tables only, in the end. They will be linked to your current dbase. I like to keep them read only, but that is your choice. Don't panic, just make a copy of the original and modify the copies. Do you have it working the way you want less querries at this point in...

Morning Bill, in the tblParamedic what are you have problems with. Structure? Only need a few things in it MedicNo, employee number are also good. MedicName is the only other major thing, you can also have addresses and telephones for general use. Then Just add MedicNo the the desired table...

Morning Mstref, you are correct on that point, but this was just meant as an alternative, besides like like that three tries and out action that this has.

I like what you said, SJ. I would go a little futher, I would also add a checkbox, chkExist, a date field DateChecked, and a txtbox, CkeckedBy. Both the last two fields could automatically filled in when the check box is checked. That way you would know who checked what and when, it is the...

Nice job, MStef, check out this for a little something different, there is a nice password demo here: http://www.candace-tripp.com/_pages/access_downloads.asp hth.

First in the relationships I almost always check all three checkboxes, cadcade delete and update and referential integrety. First thing is decide whether you want a separate dbase for the archived, deleted/cancelled records or same? With a separate dbase, you won't even know they are separate...

I do it a little differently especially when I archive the "deleted" records, which are in a different dbase, but I you like it can be in the same. I have an append query append the data to the archive table and then I have a delete query delete the data from the current table. Works very well...

Not really scraping, yet. Just use the method I previously mentioned to get the data into the form and just see if it works or maybe modify it a little bit and maybe then it will work for you. Sense it is a copy of the current dbase who cares what damage is done to it. If it works change it's...

Have you thoguht about making a copy of the dbase and striping the query? See if it works with out, it won't matter if it doesn't work, it is a copy. Just a thought. hth.

I would try them just after the DIm statement and just before the End Sub. I have heard of this before, I think this took care of it but I am not positive. Trying to get around system warning is always a pain in the butt. What I usually will do if I need it, is turn off the notinlist and in...

A few questions, is the ProfileID the PKey in the main table, Profiles? I am a little confussed on why you are using a query for the main form, I usually use the table. Are the Master / Child links properly assigned. In the subform, I usually build a little query in the datasource. I have...

Just a simple thought, have you tried adding: DoCmd.SetWarnings False Just don't forget to turn them back on. hth.

This was posted somewhere else and somehow got over here. Sorry.

Glad to see everything is working for you. This is the second time in a week that XP has been the culperate in a problem. The leason I am learning is not to use PC's with XP, ExPerimental, on them.

I have was just checking, you would be surprised at some of the table structures I have come across, and yes they have cause problems. When trying to fix something I alway start in the beginning, whcih in a dbase is the tables and then go from there. Maybe try this, make a copy of the dbase...

When I get strange Access behavior, which is not to often, I rename the old dbase and create a new blank dbase, then import everything into it, do a C&R and I am usually off and fling. Every now and then Access will go nutsy Cue-cue, I can not explain it, unless you did some modifications...

No, well at least when the table are properly constructed. You might want to read up on table normalization here: http://www.microsoft-accesssolutions.co.uk/table-of-contents.htm When your tables are right everything runs better. hth.