Replies

Many thanks. Just what i wanted.

Perfect. Thanks – what more can I say?

Perfect. Thanks – what more can I say?

I have the same problem. Deleting the Data key solved it – I thought. Until I found that this process had unticked the “Prompt to save changes to normal.dot”. When that was turned back on the problem returned. How do I uninstall the MS Reader option (if this will solve the problem)?

I have the same problem. Deleting the Data key solved it – I thought. Until I found that this process had unticked the “Prompt to save changes to normal.dot”. When that was turned back on the problem returned. How do I uninstall the MS Reader option (if this will solve the problem)?

Thanks Mary. I did not see the unlabelled box for the time. I was trying to enter the date and time in the date box like you could in earlier versions. Problem solved.

Thanks Mary. I did not see the unlabelled box for the time. I was trying to enter the date and time in the date box like you could in earlier versions. Problem solved.

The text file probably has something diferent in the first or second row and this can throw Excel. A workaround is to open the text file with excel rather than pasting it. This wil open the parser and you can set the separators, header rows and so on.

1. File names are file names. Just change the file name in explorer to Elegant Resume.dot or whatever. It must end in .dot otherwise it may not be recognised as a template. The elegant resume which is provided with Word is not a template, it is a wizard. Buildiing a wizard is more complex but can be much more powerful than a template.

2. It would be better to use a checkbox control from the controls toolbar and attach code to it do delete the watermark.

3. You can achieve something like this with fill-in fields. They have default text which you can overwrite. Others may have superior ideas.

Try this

I have moved the relationship diagram around – that make no difference to anything.

I have created a form which does more-or-less what you want.

It needs some further development as it relies on the access navigation buttons which are not ideal, but it may show you a way forward.

Ah. More info. In that case you will need the separtate price table but it will have a one to meny relationship, not one to one. (Many on the Price side). I would take out the duplicate info. Take the part number out of the Price table, and take the Vendor out of the Parts table.

You have two tables with a one to one relationship and much of the same data. Is there any reason you cannot add the Cost and Retail fields to the Parts table and do away with the Price table? This would make all you are trying to do much easier.

Also you are likely to run into trouble using field names the same as control names. I know that is how access sets them up but it is really worth changing the control VendorID to tboVendorID etc., to avoid confusing yourself and access about what you are referring to.

You probably need, instead of the vendor form, a combobox on your Price form. That way you only have the one form. The combobox would be unbound and use the vendors table as its list source. You would then use its change event to set a filter on the form. The form will then show all part numbers for that vendor.

You will need to deal with vendors not in the list, and with partnumbers not in the list or not allocated to that vendor yet. I would do those by putting on AddNewRecord buttons and making sure the linking information to vendor number is filled in in code for each new record.

Up to 50 should be OK if there are not too many calls, however it can be impacted by a lot of factors such as network speed, size of tables, whether you use subdatasheets(this can be a real killer) and, of course, how many entries are being made.

The simplest answer would be to upgrade the back end to Sql server.

Up to 50 should be OK if there are not too many calls, however it can be impacted by a lot of factors such as network speed, size of tables, whether you use subdatasheets(this can be a real killer) and, of course, how many entries are being made.

The simplest answer would be to upgrade the back end to Sql server.

It depends on who you are logged into the workgroup as. If you are logged in as a member of Admins you will have full access. If you go to another computer and do not log into the workgroup you are automatically in System.mdw as Admin. If you have not transferred ownership of the database from Admin to another user and removed the rights of Admin you have achieved nothing. The database is not secured.

Check who the database owner is. and make sure it is not Admin

Make sure the workgroup used for security is not called System.mdw

Make sure Admin in the workgroup is not a member of admins and does not have full rights.

(I think this is right, but there may be minor differences between versions)