Recent content by TinkerMan

Thanks your input again, I really appreciate it :) This is what I have concluded as well, so my suppliers already exist in a separate table. I completely agree with your point of view as I try to generalize where possible, but I’m not quite sure this applies to my specific case. I’ll try to...

Thanx for the replies :) Sorry my feedback was a bit late, but I was away for the weeked :) This is a good suggestion, but it will limit me to only have one link (if I get your point) - so I can only use one other recipe as base, not many (yes, I know I making this complicated in addition :)...

I have a problems which seems simple, but it's made me doubt everything I have learned about this; I suddenly find myself unable to grasp what I belive is a very small and easy solution, but I cannot!! (Either that or I have stumbled upon a real conseptual problem without realising it :) ) This...

Hi gemma-the-husky :) Since I can only replace the FE, I was hoping to run all updates from from the FE. The problem as I see it on upgrading from the BE is that you need to have the code for upgrading available in the BE. That means that if you bring a new version of the BE with the upgrade...

Thanks Robert88 :) Yes, that would definately make things easier :D Also I would not have to comprismise security by changing the ownership of the tables, which one of the core elements of the security. So what you're suggesting is to make a user in the customer workgroup that has permissions...

Hi Robert88 :) Sorry for being so inaccurate: As you mention ALTER TABLE statements is what I want to use. However, my problem is that my database is secured, so I do not have access to change the table object, as I'm not the owner (as described in my initial post). Because this upgrade happens...

Hi Robert88 :) Thanx for your reply. Sorry for not specifying more clearly: I'm not upgrading Access, but my own database; My scenario is that i have a version out at customers. I then make a newer version with more functionality and I need to deploy it. FE I can just replace, but the BE has...

Hi :) (A2K format, but running on XP, etc) I have used Microsoft’s Security FAQ and recommendations on this forum and build a split database; secured with one worgroup file for development and one for customers: what is the most appropriate way to upgrade the backend database content (tables...

hi :) I'm using 2003 and 2000 and want to have "Auto Compact" on, so when users exit, it will compact and repair. I'm using the security measures described in the Access Security FAQ and in this forum. I therefore have 2 workgroup files, one for development and one for distribution. My own...

Thanks for your feedback :) The only thing that still is unclear, is that my database has implemented full security, which means that nobody can access my db without authenticating. This means that the shortcut must also be able to log in...Is there a good way of solving that? Also, any idea...

Hi all :) I'm planning to use the "compact on exit" functionality to keep my db's neat. I have understood that I also have to grant "Exclusive mode" to the database object to the users of my db (not to Users group, but my own users group). Does this have a security implication? As I'm running...

My frustration is definitively on the way up, as A 2003 keeps crashing, without giving me any clues as to why. I have an A2K database (actually 3) split into FE/BE. Works like a charm with A2K and A2002(XP), but I'm having serious problems with A2003. First off; does anybody know how to...

Hi all :) I'm in need of some expertise here (running A2K on XP pro): I've got a db, split into a FE and BE. I have a workgroup file built to the spec of the Access security faq. At the moment I'm doing development, and I was creating the shourtcuts to start access with the workgroup file. For...

Thanks ghudson :) This is a very important point, although I have always done that, exactly for that reason, for all my db's. After keeping this on the backburner over night, I seem to have concluded that option 2 is the only alternative that does not by default invalidate the security. I'll...

Hi :) I'm currently in the process of testing security before shipping my database off. I have read the access security faq, but I'm not sure which option to go for. The main factor that makes me doubt, is that the db will be sent to locations that I will not be able to physically get to...