Adding "attachments" field to table is "corrupting" it?

[starrcruise]

I am revamping a DB in 2007 that was created in 2007. I have updated 4 tables, but with 2 of them, when I add the attachements field to the table, it seems to corrupt the table. Why do I think this? Because when I add the field, and then open the form attached to the table, none of the controls are matching their control source, although the control source is correct. I accidentally discovered this. so I went back and forth, deleting the attachment field, adding the attachments field. I even recreated a new table and appended the info and THEN added the attachment field and same thing. The other two were fine when I added the attachment. Just want to know if there is something freaky I am doing that I don't know about, or if anyone else has had this problem. Unfortunately, I REALLY need the attachment fields for these tables. thank you!

 

[vbaInet]

Try creating a new Access 2007 database shell and importing all your objects into it, then create a new table in that new db and add the Attachment field in that table.

Do you really need to save files in the attachment field? Here is an alternative:

http://office.microsoft.com/en-us/access-help/store-images-in-a-database-HP005280225.aspx
http://office.microsoft.com/en-us/a...s-forms-reports-and-controls-HA001147204.aspx

Note: It's not limited to just images.

 

[starrcruise]

Thank you for your reply. I forgot to mention that I split this DB. So I'll do the above in a different backend. I hope that works! I am also thinking about your suggestion via the links. The attachments are not images, but emails and documents, and they already live in another folder on a network drive. So that may also be the answer, except that everyone in our department has access to this network drive and folders and I have had folders accidentally moved or deleted. However, both suggestions are excellent, as I know this DB is going to get bigger and bigger. There may be a possibility that I have to put this DB on Sharepoint in the future. Would there be an issue with any of this? I haven't even examined what moving it to Sharepoint would require other than Sharepoint would allow a much bigger DB. Thanks again!

 

[vbaInet]

I don't know much of Sharepoint to be able to advise but from my little knowledge I don't see a problem with using this approach in a Sharepoint server. Sharepoint simply handles the data and with the second approach it's how it's implemented in the Front End that matters - i.e. a simple pointer to the file's location.

Also, if files were mistakenly moved, you can run a query to check whether file paths are valid or not.