Search results

  1. E

    Best practice on hotel room allocations

    alktrigger - I am trying to take your approach. I have a booked rooms table (not equivalent to bookings because bookings can have several rooms) but I have an additional issue which is the allocation. The company gets a room allocation, say 140 rooms of a particular type and 50 of another for...
  2. E

    Best practice on hotel room allocations

    Thank you. That's given me some idea of an approach, although this would require me to set up a record for each room and in my case specific dates it is available because we have an allocation and it is limited in time (it's not all year). I was hoping to avoid such database chores such as...
  3. E

    Best practice on hotel room allocations

    Thanks alktrigger. There are compatibility issues. Could you send the 2007 version - I'm using Access 2007. Thanks economyman
  4. E

    Best practice on hotel room allocations

    I am attaching the current db architecture. It's just the beginning but really my question relates mainly to the allocation table. At the moment as can be seen in the attached picture, it includes an allocation per room type per date range. Would I be better off having an allocation per room...
  5. E

    Best practice on hotel room allocations

    Maybe I should reiterate my quesiton - should I create a multi-dimensional array of some sort and record for each night and each room a booking ID so it is clearly visible how many nights /rooms are taken / free or should this be calculated each time from the underlying allocation and booking...
  6. E

    Best practice on hotel room allocations

    Hi I'm building a DB to manage a seasonal booking system for a tour operator that runs some special events during the year at several hotels. The operator receives allocations of rooms for a given period (from date to date) including sometimes several different room types per hotel per event...
  7. E

    export to text but only certain number of records

    Wow - I could swear I tried that earlier but I probably had something else not quite right - it worked now. Thank you both of you - great piece of code and great solution - saved me a headache and makes me want to code again!
  8. E

    export to text but only certain number of records

    Same thing: Starts with Public Function, then goes to StrPath, then Set Rs - ... and the error comes again. Maybe this helps: I have added an Option Explicit and then I get Variable not defined error on the first line of the Public Function. I would like to solve this because it is bugging me...
  9. E

    export to text but only certain number of records

    Actually, the module is saved just as Module1 and the function as far as I can tell is called SplitTableOrQuery and comes under the General section so I don't know what else I could be doing wrong.
  10. E

    export to text but only certain number of records

    I call the function from a macro using Run Code and the argument: SplitTableOrQuery("May09Export",65000) Then I have a module as follows: Public Function SplitTableOrQuery(TableOrQueryName As String, MaxRows As Long) Dim Rs As DAO.Recordset Dim fileNum As Long Dim TxtStr As String Dim nIndex...
  11. E

    export to text but only certain number of records

    When I did that it gives me another error that it cannot find the table or query. I am using a select query for the recordset and have checked the spelling, etc.
  12. E

    export to text but only certain number of records

    That works now - big thanks. Now I am stuck on: Set Rs = CurrentDb.OpenRecordset(TableOrQueryName) - I get an Invalid Operation error on this line of code. Any ideas? Thank you economyman
  13. E

    export to text but only certain number of records

    Hi. I had a similar need. Well actually my problem is I have a recordset with more than 750K records which I want to export into Excel to send to a customer. Excel 2007 can take that but for some reason when I try to export from Access it says that the clipboard cannot take more than 65K...
  14. E

    Changing Data Type Once DB populated

    Indeed it is a a table level lookup. As I said, I set up this DB when I was just starting off with Access. In newer databases I have not done this but the truth is that at the moment I am only using this DB in its raw format without forms. I write queries including action queries and then remove...
  15. E

    Changing Data Type Once DB populated

    MSAccessRookie's proposal is the perfect solution for me - I should have thought of that myself but there you go. You are a more experienced rookie then me. :) Changing the datatype as datAdrenaline suggests is what I tried before starting this thread - it didn't work, which is not surprising...
  16. E

    Changing Data Type Once DB populated

    Hi There I have a DB with several thousand records in a table representing SIM card information. One of the fields is a FK Customer field. It is based on a lookup from the Customer table however for some reason unbeknown to me the data type created was Text instead of Number, even though the...
  17. E

    SIM ID or Autonumber as PK

    Thank you for that George. It makes sense. Cheers! Michael
  18. E

    SIM ID or Autonumber as PK

    Hi Can someone tell me if I am better off using an Autonumber as the PK in a table of SIM cards (GSM phone cards). Each SIM has a globally unique SIM ID number. It has a certain structure however from my perspective I don't care too much about the structure. I have a list of SIMs we have...
Back
Top Bottom