APPEND QUERY RUNS ON ITS OWN BUT NOT IN A MACRO
in [Tables]
|
From: Gina Whipp on 10 Dec 2009 18:55 Allan, I THINK this applies to Access 2000, I forget when this started. To check the Macro Settings, which is via Access not via the network, follow these steps... 1. Open any database 2. Go to Tools... Macro... click Security... 3. On the machine that works check the setting but it sounds like it's set to Low. Insure all the other machines are set the same way. Yep, you get a message about being unsafe... just say Yes or OK. Let's see if that's the problem. -- Gina Whipp "I feel I have been denied critical, need to know, information!" - Tremors II http://www.regina-whipp.com/index_files/TipList.htm "ALLAN_ASHFORD via AccessMonster.com" <u56735(a)uwe> wrote in message news:a066b80b970e3(a)uwe... > Hi Gina > > Access 2000 > > Being self-taught I'm not sure what you mean by "macro settings at in each > front end or at each location?". However the database from which the > problem > database was derived runs in parallel presumeably under the same > configuration (local & network) without any problem as the one that is > giving > the problem so the macro settings (whatever they are) should be the same. > Can > you please give me some pointers to check? > > Sorry I can't be of more help, but having used Access for 15 years this is > the first time I have come across a problem I haven't managed to solve. > > Allan > > Gina Whipp wrote: >>Allan, >> >>Forgot to ask Access version? >> >>And if I am understanding you... running the query appends the records >>BUT >>running it from the macro does not work. Since the query appears fine. >>What are the macro settings at in each front end or at each location? >> >>> Hi Gina >>> >>[quoted text clipped - 35 lines] >>>>>>>>> >>>>>>>>> Allan Ashford > > -- > Message posted via AccessMonster.com > http://www.accessmonster.com/Uwe/Forums.aspx/access-tablesdbdesign/200912/1 >
From: AccessVandal via AccessMonster.com on 10 Dec 2009 20:18 Macro Security is only avialable in 2003 and 2007. For 2000 there's no security for macros. What Gina is refering to is the end users PC, what version are they using? If it is 2003 or 2007, you might want to ask them to to disable macros for this test. If they are using 2007, make sure the database is in Trusted locations. You might want to check for WorkGroup Security just in case even the owner/user or the Admin user setting was incorrect where the user might not be able to execute the database macro. You can go to the security - user and group permissions - object type - select the your macro name and make sure they have the neccessary permission. They are open/run, read design, modify design, administer. I doubt it, as it is very unlikely that someone might change this, but than again who knows? (even if you don't use workgroup security, it still worthwhile to check just in case someone setup user security accidentaly). 2007 format databse(accdb) does not support workgroup security. ALLAN_ASHFORD wrote: >Hi Gina > >Access 2000 > >Being self-taught I'm not sure what you mean by "macro settings at in each >front end or at each location?". However the database from which the problem >database was derived runs in parallel presumeably under the same >configuration (local & network) without any problem as the one that is giving >the problem so the macro settings (whatever they are) should be the same. Can >you please give me some pointers to check? > >Sorry I can't be of more help, but having used Access for 15 years this is >the first time I have come across a problem I haven't managed to solve. > >Allan -- Please Rate the posting if helps you. Message posted via AccessMonster.com http://www.accessmonster.com/Uwe/Forums.aspx/access-tablesdbdesign/200912/1
From: Gina Whipp on 10 Dec 2009 20:23 AccessVandal, Thanks, I wasn't sure if that was available in 2000. -- Gina Whipp "I feel I have been denied critical, need to know, information!" - Tremors II http://www.regina-whipp.com/index_files/TipList.htm "AccessVandal via AccessMonster.com" <u18947(a)uwe> wrote in message news:a067a0b8d850a(a)uwe... > Macro Security is only avialable in 2003 and 2007. For 2000 there's no > security for macros. What Gina is refering to is the end users PC, what > version are they using? If it is 2003 or 2007, you might want to ask them > to > to disable macros for this test. If they are using 2007, make sure the > database is in Trusted locations. > > You might want to check for WorkGroup Security just in case even the > owner/user or the Admin user setting was incorrect where the user might > not > be able to execute the database macro. You can go to the security - user > and > group permissions - object type - select the your macro name and make sure > they have the neccessary permission. They are open/run, read design, > modify > design, administer. I doubt it, as it is very unlikely that someone might > change this, but than again who knows? (even if you don't use workgroup > security, it still worthwhile to check just in case someone setup user > security accidentaly). 2007 format databse(accdb) does not support > workgroup > security. > > ALLAN_ASHFORD wrote: >>Hi Gina >> >>Access 2000 >> >>Being self-taught I'm not sure what you mean by "macro settings at in each >>front end or at each location?". However the database from which the >>problem >>database was derived runs in parallel presumeably under the same >>configuration (local & network) without any problem as the one that is >>giving >>the problem so the macro settings (whatever they are) should be the same. >>Can >>you please give me some pointers to check? >> >>Sorry I can't be of more help, but having used Access for 15 years this is >>the first time I have come across a problem I haven't managed to solve. >> >>Allan > > -- > Please Rate the posting if helps you. > > Message posted via AccessMonster.com > http://www.accessmonster.com/Uwe/Forums.aspx/access-tablesdbdesign/200912/1 >
From: ALLAN_ASHFORD via AccessMonster.com on 10 Dec 2009 21:20 Hi Gina I'll check security out in the morning (I'm UK based nand it's now 2.15 am). But I'm running both databases on the same PC under Access 2000 and both with linked tables onto the same other PC across my own network, i.e. I'm still at the testing stage, so none of the modifications have been loaded onto the clients's PCs. Allan Gina Whipp wrote: >AccessVandal, > >Thanks, I wasn't sure if that was available in 2000. > >> Macro Security is only avialable in 2003 and 2007. For 2000 there's no >> security for macros. What Gina is refering to is the end users PC, what >[quoted text clipped - 36 lines] >>> >>>Allan -- Message posted via http://www.accessmonster.com
From: Gina Whipp on 10 Dec 2009 22:31
Allan, Then the Macro Security is not an option if using Access 2000. How is the macro run? Is it a button on a form? What is the code? -- Gina Whipp "I feel I have been denied critical, need to know, information!" - Tremors II http://www.regina-whipp.com/index_files/TipList.htm "ALLAN_ASHFORD via AccessMonster.com" <u56735(a)uwe> wrote in message news:a0682ab3954ac(a)uwe... > Hi Gina > > I'll check security out in the morning (I'm UK based nand it's now 2.15 > am). > But I'm running both databases on the same PC under Access 2000 and both > with > linked tables onto the same other PC across my own network, i.e. I'm still > at > the testing stage, so none of the modifications have been loaded onto the > clients's PCs. > > Allan > > Gina Whipp wrote: >>AccessVandal, >> >>Thanks, I wasn't sure if that was available in 2000. >> >>> Macro Security is only avialable in 2003 and 2007. For 2000 there's no >>> security for macros. What Gina is refering to is the end users PC, what >>[quoted text clipped - 36 lines] >>>> >>>>Allan > > -- > Message posted via http://www.accessmonster.com > |