Re: Access DB: Preventing duplicates! arrrh
chota sa ... ??? ... you will .... ah ... nevermind ... I don't want to ruin it for the guy anymore .... I'm seriously looking into the solution ...
Re: Access DB: Preventing duplicates! arrrh
Exactly! Its only cross checking **one **field cause the DLlookup function checks only one field, which is the first parameter of the function. Get it? So you need something that would check the user input with all the three fields in the table. And how would you do that? .. hmm … a query? Why don’t you run a query? its the same as using the script isn’t it? Why are you insisting on using the VB script, I need a software engineer’s answer …
Re: Access DB: Preventing duplicates! arrrh
CM, why don't u suggest a calendar like interface where she can cross check by rooms or by time slot. So, in one UI she sees the week or month and clicks on a time slot and sees which room is available. In the second UI she looks at all the rooms and she can pick a room and see when its available. Let me see if i can create a picture of it and post it up. Might not be till I get home tho.
Re: Access DB: Preventing duplicates! arrrh
That's what I told him .. he's got the wrong design for this solution ... the user would go crazy trying out different options .. khair
Re: Access DB: Preventing duplicates! arrrh
Here's one version:
[thumb=H]bookings20076_7541792.JPG[/thumb]
Potentially she can do this in Outlook. Maybe in Outlook you can tap into the Access database, who knows. Just a suggestion to start thinking out of the box (or atleast get your client to). Good luck.
Here's the other view:
[thumb=H]bookings220076_7176459.JPG[/thumb]
Sorry for the rough sketch!
Re: Access DB: Preventing duplicates! arrrh
I like that suggestion tofibaba, i'll just need to think about how i'll need to restructure my database in order to implement it.
Re: Access DB: Preventing duplicates! arrrh
kaash meree baat koee samajh pae hae CM I am sure you are well aware of my intention at this very moment 
I suggested the samething but in different design and order, this thing can happen in various style. But CM remind me of pakistani soldiers, who go by the order 
Re: Access DB: Preventing duplicates! arrrh
SELECT tbl.ID, tbl.TeamPeople, tbl.DateRecieved, tbl.ProspectName, tbl.[Type Of Business], tbl.AmountofCredit
FROM tbl
WHERE (((tbl.ID) In (SELECT [ID] FROM [tbl] As Tmp GROUP BY [ID],[TeamPeople],[DateRecieved] HAVING Count(*)>1 And [TeamPeople] = [tbl].[TeamPeople] And [DateRecieved] = [tbl].[DateRecieved])))
ORDER BY tbl.ID, tbl.TeamPeople, tbl.DateRecieved;
query would be something like this, I am using my own table fields. Since, ID can not be duplicate its an autonumber, leave out that field. I just used it for an example. Hopefully, it will make sense to you. Now, what else can you do, beside only creating query and putting it in load events. You can also generate a search engine, where you would be needing a query and as well as vb script. This would be another form and she would be able to search her way through and locate the availability of the room depending on different fields. I have one hellova search engine, that I have used several times, but in diff design. If you want that, I can you pass u that file.