|
| If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|||||||
|
|
|
Thread Tools | Display Modes |
|
#1
May 3rd, 2004, 02:05 PM
|
|||
|
|||
How do I make DB accessable to many people at once
I have a DB with many tables (1 for each dept) they are
spead sheets that they leave open to log closings. The prob is: How do I set it up so all areas can have the table open for their particular station and be able to enter data without getting the read only flag? 
|
|
#2
May 3rd, 2004, 04:00 PM
|
|||
|
|||
|
How do I make DB accessable to many people at once
"1 for each dept" indicates that most likely, your database is incorrectly
designed and structured. Suggest you read up on Relational Database Design Theory first which will save you a lot of time later. (Hint: don't use database Tables as Excel Spreadsheets!) -- HTH Van T. Dinh MVP (Access) "The Cat" wrote in message ... I have a DB with many tables (1 for each dept) they are spead sheets that they leave open to log closings. The prob is: How do I set it up so all areas can have the table open for their particular station and be able to enter data without getting the read only flag?
|
|
#3
May 3rd, 2004, 04:58 PM
|
|||
|
|||
|
How do I make DB accessable to many people at once
I don't think you understood the question...I am no
ameteur at building databases and am very familar with Relational design theory. Thanks for nothing!!!!!!! -----Original Message----- "1 for each dept" indicates that most likely, your database is incorrectly designed and structured. Suggest you read up on Relational Database Design Theory first which will save you a lot of time later. (Hint: don't use database Tables as Excel Spreadsheets!) -- HTH Van T. Dinh MVP (Access) "The Cat" wrote in message ... I have a DB with many tables (1 for each dept) they are spead sheets that they leave open to log closings. The prob is: How do I set it up so all areas can have the table open for their particular station and be able to enter data without getting the read only flag? .
|
|
#4
May 3rd, 2004, 06:41 PM
|
|||
|
|||
|
How do I make DB accessable to many people at once
If you were as familiar with relational database theory as you suggest, then
you would NOT create "1 table for each dept", but would create one table with a field to indicate which department a given record is for. On reason you may be getting the "read only flag", could have to do with folder permissions where your database is stored. Make sure everyone who uses the database has full read/write permissions to the folder. -- Lynn Trapp MS Access MVP www.ltcomputerdesigns.com Access Security: www.ltcomputerdesigns.com/Security.htm wrote in message ... I don't think you understood the question...I am no ameteur at building databases and am very familar with Relational design theory. Thanks for nothing!!!!!!! -----Original Message----- "1 for each dept" indicates that most likely, your database is incorrectly designed and structured. Suggest you read up on Relational Database Design Theory first which will save you a lot of time later. (Hint: don't use database Tables as Excel Spreadsheets!) -- HTH Van T. Dinh MVP (Access) "The Cat" wrote in message ... I have a DB with many tables (1 for each dept) they are spead sheets that they leave open to log closings. The prob is: How do I set it up so all areas can have the table open for their particular station and be able to enter data without getting the read only flag? .
|
|
#5
May 3rd, 2004, 07:53 PM
|
|||
|
|||
|
How do I make DB accessable to many people at once
It's like you said, I stated it incorrectly...but thanks
because my problem was in the permissions folder...works great now--again thank you. "The Cat" -----Original Message----- If you were as familiar with relational database theory as you suggest, then you would NOT create "1 table for each dept", but would create one table with a field to indicate which department a given record is for. On reason you may be getting the "read only flag", could have to do with folder permissions where your database is stored. Make sure everyone who uses the database has full read/write permissions to the folder. -- Lynn Trapp MS Access MVP www.ltcomputerdesigns.com Access Security: www.ltcomputerdesigns.com/Security.htm wrote in message ... I don't think you understood the question...I am no ameteur at building databases and am very familar with Relational design theory. Thanks for nothing!!!!!!! -----Original Message----- "1 for each dept" indicates that most likely, your database is incorrectly designed and structured. Suggest you read up on Relational Database Design Theory first which will save you a lot of time later. (Hint: don't use database Tables as Excel Spreadsheets!) -- HTH Van T. Dinh MVP (Access) "The Cat" wrote in message ... I have a DB with many tables (1 for each dept) they are spead sheets that they leave open to log closings. The prob is: How do I set it up so all areas can have the table open for their particular station and be able to enter data without getting the read only flag? . .
|
|
#6
May 3rd, 2004, 09:51 PM
|
|||
|
|||
|
How do I make DB accessable to many people at once
I'm glad you got it working then. For future reference, you should be more
careful about jumping on a great guy like Van Dinh. He read your question as you originally stated it and made the same assumption that, probably, most every one did, and was only trying to help you out. He may likely be reluctant to help you next time he sees a message from you, and that would be your loss. -- Lynn Trapp MS Access MVP www.ltcomputerdesigns.com Access Security: www.ltcomputerdesigns.com/Security.htm wrote in message ... It's like you said, I stated it incorrectly...but thanks because my problem was in the permissions folder...works great now--again thank you. "The Cat" -----Original Message----- If you were as familiar with relational database theory as you suggest, then you would NOT create "1 table for each dept", but would create one table with a field to indicate which department a given record is for. On reason you may be getting the "read only flag", could have to do with folder permissions where your database is stored. Make sure everyone who uses the database has full read/write permissions to the folder. -- Lynn Trapp MS Access MVP www.ltcomputerdesigns.com Access Security: www.ltcomputerdesigns.com/Security.htm wrote in message ... I don't think you understood the question...I am no ameteur at building databases and am very familar with Relational design theory. Thanks for nothing!!!!!!! -----Original Message----- "1 for each dept" indicates that most likely, your database is incorrectly designed and structured. Suggest you read up on Relational Database Design Theory first which will save you a lot of time later. (Hint: don't use database Tables as Excel Spreadsheets!) -- HTH Van T. Dinh MVP (Access) "The Cat" wrote in message ... I have a DB with many tables (1 for each dept) they are spead sheets that they leave open to log closings. The prob is: How do I set it up so all areas can have the table open for their particular station and be able to enter data without getting the read only flag? . .
|
|
#7
May 4th, 2004, 03:07 PM
|
|||
|
|||
|
How do I make DB accessable to many people at once
He may be a great guy, but does not have a very good way
of coming across to a person....nobody likes to be made to sound dumb! -----Original Message----- I'm glad you got it working then. For future reference, you should be more careful about jumping on a great guy like Van Dinh. He read your question as you originally stated it and made the same assumption that, probably, most every one did, and was only trying to help you out. He may likely be reluctant to help you next time he sees a message from you, and that would be your loss. -- Lynn Trapp MS Access MVP www.ltcomputerdesigns.com Access Security: www.ltcomputerdesigns.com/Security.htm wrote in message ... It's like you said, I stated it incorrectly...but thanks because my problem was in the permissions folder...works great now--again thank you. "The Cat" -----Original Message----- If you were as familiar with relational database theory as you suggest, then you would NOT create "1 table for each dept", but would create one table with a field to indicate which department a given record is for. On reason you may be getting the "read only flag", could have to do with folder permissions where your database is stored. Make sure everyone who uses the database has full read/write permissions to the folder. -- Lynn Trapp MS Access MVP www.ltcomputerdesigns.com Access Security: www.ltcomputerdesigns.com/Security.htm wrote in message ... I don't think you understood the question...I am no ameteur at building databases and am very familar with Relational design theory. Thanks for nothing!!!!!!! -----Original Message----- "1 for each dept" indicates that most likely, your database is incorrectly designed and structured. Suggest you read up on Relational Database Design Theory first which will save you a lot of time later. (Hint: don't use database Tables as Excel Spreadsheets!) -- HTH Van T. Dinh MVP (Access) "The Cat" wrote in message ... I have a DB with many tables (1 for each dept) they are spead sheets that they leave open to log closings. The prob is: How do I set it up so all areas can have the table open for their particular station and be able to enter data without getting the read only flag? . . .
|
|
#8
May 5th, 2004, 05:39 AM
|
|||
|
|||
|
How do I make DB accessable to many people at once
If he'd wanted to make you "sound dumb", here is what he would have said
initially: "Your reference to having 1 table for each department, makes it instantly clear that you do not understand the simplest and most basic principles of database normalization." Here is what he actually said: "(1 for each dept) indicates that most likely, your database is incorrectly designed and structured. Suggest you read up on Relational Database Design Theory first, which will save you a lot of time later." You responded to that polite & appropriate suggestion with: "Thanks for nothing!!!!!!!" Here's how I suggest you proceed. (a) stop wingeing, (b) apologize to him for being such a prat, and (c) be more polite in future to more-knowledgable people who give of their help in these newsgroups for free. Just my 2c worth. TC wrote in message ... He may be a great guy, but does not have a very good way of coming across to a person....nobody likes to be made to sound dumb! -----Original Message----- I'm glad you got it working then. For future reference, you should be more careful about jumping on a great guy like Van Dinh. He read your question as you originally stated it and made the same assumption that, probably, most every one did, and was only trying to help you out. He may likely be reluctant to help you next time he sees a message from you, and that would be your loss. -- Lynn Trapp MS Access MVP www.ltcomputerdesigns.com Access Security: www.ltcomputerdesigns.com/Security.htm wrote in message ... It's like you said, I stated it incorrectly...but thanks because my problem was in the permissions folder...works great now--again thank you. "The Cat" -----Original Message----- If you were as familiar with relational database theory as you suggest, then you would NOT create "1 table for each dept", but would create one table with a field to indicate which department a given record is for. On reason you may be getting the "read only flag", could have to do with folder permissions where your database is stored. Make sure everyone who uses the database has full read/write permissions to the folder. -- Lynn Trapp MS Access MVP www.ltcomputerdesigns.com Access Security: www.ltcomputerdesigns.com/Security.htm wrote in message ... I don't think you understood the question...I am no ameteur at building databases and am very familar with Relational design theory. Thanks for nothing!!!!!!! -----Original Message----- "1 for each dept" indicates that most likely, your database is incorrectly designed and structured. Suggest you read up on Relational Database Design Theory first which will save you a lot of time later. (Hint: don't use database Tables as Excel Spreadsheets!) -- HTH Van T. Dinh MVP (Access) "The Cat" wrote in message ... I have a DB with many tables (1 for each dept) they are spead sheets that they leave open to log closings. The prob is: How do I set it up so all areas can have the table open for their particular station and be able to enter data without getting the read only flag? . . .
|
|
#9
May 5th, 2004, 05:00 PM
|
|||
|
|||
|
How do I make DB accessable to many people at once
"TC" wrote in message ...
(c) be more polite in future to more-knowledgable people who give of their help in these newsgroups for free. Even knowledgeable people can get things wrong, particularly when they are working for free, so be careful when rushing to their defence simply because they have letters after their name. This is how I see it: Q. I have a DB with many tables, they are spead sheets A. don't use database Tables as Excel Spreadsheets Did you consider the possibility that they actually are spreadsheets? Here's a bit of knowledge for you: in Jet you can create a 'linked table' where the source is an Excel spreadsheet and this is legitimate usage. Now, in the above case there is a good chance we are talking about actual Excel spreadsheets and the tables in question are linked tables. So, MVP or no, saying don't use a database table which is a linked Excel spreadsheet as a spreadsheet is a dumb answer.
|
|
#10
May 6th, 2004, 12:03 AM
|
|||
|
|||
|
How do I make DB accessable to many people at once
Read the original question!
Are the Tables linked Excel spreadsheets as mentioned by the original poster? If they were, the "database" with linked Excel spreadsheets is most likely flat / non-relational and my advice is actually the *right* advice. IMHO, not knowing Relational Database Design Theory is not dumb, simply needing an advice to go the right direction. It is up to the original poster to take the advice whichever way he likes (or doesn't like). I think it is rather stupid to assume things to create a scenario just to suit your particular answer. Have you tried to use Excel spreadsheet relationally besides simple "lookups"? BTW, Excel spreadsheets can have mixed data types in one Column while Access can only have one data type in a Field. You may not be aware that editing data using a linked Table which comes from an Excel spreadsheet can corrupt the Excel file (at least in A2K0). Ask experienced database developers whether they seriously use Excel spreadsheets as permanent linked Tables in their database development. If you do use Excel spreadsheets as the permanent source for your database development, good luck to you and your clients! I am sure your clients will be happy with Tables that are limited to 64K Records each. Perhaps, you develop mostly "toy" databases??? -- Van T. Dinh MVP (Access) "jamieuk" wrote in message om... "TC" wrote in message ... (c) be more polite in future to more-knowledgable people who give of their help in these newsgroups for free. Even knowledgeable people can get things wrong, particularly when they are working for free, so be careful when rushing to their defence simply because they have letters after their name. This is how I see it: Q. I have a DB with many tables, they are spead sheets A. don't use database Tables as Excel Spreadsheets Did you consider the possibility that they actually are spreadsheets? Here's a bit of knowledge for you: in Jet you can create a 'linked table' where the source is an Excel spreadsheet and this is legitimate usage. Now, in the above case there is a good chance we are talking about actual Excel spreadsheets and the tables in question are linked tables. So, MVP or no, saying don't use a database table which is a linked Excel spreadsheet as a spreadsheet is a dumb answer.
|
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
