Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Create Table Permissions Assigned? 1

Status
Not open for further replies.

RoseV

Programmer
Mar 18, 2003
37
US
I have a problem where tables are created with a make table query. Occasionally, we run into an error where the user (and myself) are denied permission to delete the table (it is deleted and remade many times a day) before the new one is created. How can I assign (or unassign) permissions on a table manually created this way?
I posted previously – this was suggested:

I have had this problem many times, since we have a Database with about 30 Users accessing info at the same time.

For a Table that is being deleted and recreated on a continuous basis. Make that the table should be created in the each one PC's Local temp directory. Let your SQL reflect where it should create the table and you will never have problems with a conflict.


...But I don’t understand the “where” part. How do I direct where a table is created? A make table just puts it into a database – how do I “create a table in a local directory”?
 
Hi Rose!

I have suggested to you to create a Table in each ones Temp Directory Here you have the code you can put into a module or in a simple make Table query

SELECT <TableName>.* INTO <New TableName> IN 'C:\Temp\<DataBaseName>.Mdb' FROM <TableName> WHERE (((<TableName>.Date) Between #1/1/01# And #12/31/01));

In The Table that is on the Network drive create a Link to the Table in the C:\Temp Directory and there won't be any conflicts.

I hope this helps;
 
I'm guessing your database isn't split with a front end containing all the code and the forms on everybodies PC and a backend with just the data residing on the shared network drive.
Can I suggest you split your database in this manner as a matter of urgency. Splitting the dB reduces the load on the network as only the data is sent across the wires, not the forms & code too.
Splitting the database will then let you create local temp files that do not affect other users to the system.

Just my thoughts

Ben

----------------------------------------------
Ben O'Hara

&quot;Where are all the stupid people from...
...And how'd they get so dumb?&quot;
NoFX-The Decline
----------------------------------------------
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top