Search results

  1. W

    Enforce business rules though referential integrity

    Okay.. I see what you are getting at.. but it doesn't help me.. I'll explain.. I have further data that is attached to a client. This data is taken from a lookup table, and is country specific.. The principle is the same as my original post. I want to enforce business rules between tables that...
  2. W

    Renaming tables

    If there are spaces in the table names, are there also spaces in the field names ? It seems like an unnecessary piece of work, as although its not good practise to use spaces in names, your database should work fine with them. Whereas if you go down this route, you potentially can 'corrupt'...
  3. W

    Enforce business rules though referential integrity

    I am building a new project which has some core tables.. The key tables are: Countries CountryID CountryName Businesses BusinessID BusinessName CountryID Clients ClientID ClientName BusinessID CountryID I want to enforce the rule that a Business can only have clients within the same...
  4. W

    Create MDE with all menus and shift key access disabled

    I managed to get this working a while ago using using a VBA work around.. Thought I'd post up for anyone else who needs to do the same. 1. Take a copy of the MDB database file. * Use the copy for locking down as this will not be able to be opened up again once locked down. * DO NOT LOCK...
  5. W

    CITRIX - Applications

    Have you had any issues with file locking issues, maybe caused byuser sessions not being closed properly?
  6. W

    Building Multiuser Apps with Access

    I'm told UDTs consume much less memory compared to Classes as classes are treated as Variants. Correct. The code loops through each record looking for a match. Yes, it does run over a WAN. Is this important? There are constraints on the backend to enforce referential integrity etc as you'd...
  7. W

    Building Multiuser Apps with Access

    Thats a negative. No documentation. Built like this for performance reasons I'm told. Some good points there. Regarding deletes, I never build DBs with the ability to delete records. I prefer to use an archive method if needed. There are no deletes on the DBs here as far as I am aware. The...
  8. W

    Building Multiuser Apps with Access

    Yep... that is pretty much what most of the databases here are doing.
  9. W

    Building Multiuser Apps with Access

    The UDTs are loaded in to arrays not collections. They essentially read all of the data from the database and load in to memory when the app is opened, then displayed to the forms etc.. When a change is made on a form, another 'snapshot' of the data is loaded into a new UDT and both initial UDT...
  10. W

    Building Multiuser Apps with Access

    I've always setup Front Ends and Back Ends so that a copy of the Front End is distributed to each Desktop. I've now joined a new company (been here 6 months now) and the way things are done here is that one copy of the FE sits on a share and users open it from that location. This file contains...
  11. W

    Create MDE with all menus and shift key access disabled

    I've only posted one response since my initial thread.. The point is I want to create a distributable MDE application where the user cannot open objects using the shift key. I also want to disable everything except the status bar. This does not seem to be the case, on my machine at least.
  12. W

    Create MDE with all menus and shift key access disabled

    Hi vbaInet Thanks for your input. I'm not concerned about automating this at the moment, so can use the menu to set the restrictions for the moment. I have modified the code as you suggested, but it still does not work. CurrentDb.Properties("AllowByPassKey") = False
  13. W

    Create MDE with all menus and shift key access disabled

    Does anyone know how I can create an MDE with all options disabled including shift key bypass. I want to remove all options in Tools>Startup except for the status bar. I have tried using this code but am not getting anywhere with it CurrentDb.Properties("AllowByPassKey") = 0
  14. W

    DDL to create TimeStamp field

    Ok.. looks like the following code works.. Frustrating that I cannot set the default in DDL though. CurrentDb.Execute "ALTER TABLE Audit ADD COLUMN RecordCreatedDate DATE ;" CurrentDb.TableDefs("Audit").Fields("RecordCreatedDate").DefaultValue = "now()"
  15. W

    DDL to create TimeStamp field

    Same error as in my first post err.number = 3293 err.description = Syntax error in ALTER TABLE statement.
  16. W

    DDL to create TimeStamp field

    Hi BlueIshDan Thanks for helping out so far.. I tried the following two examples from this link.. CREATE TABLE Persons ( P_Id int NOT NULL, LastName varchar(255) NOT NULL, FirstName varchar(255), Address varchar(255), City varchar(255) DEFAULT 'Sandnes' ) and ALTER TABLE Persons ALTER...
  17. W

    DDL to create TimeStamp field

    Still doesn't work. GETDATE is a SQL Server function. You also need to specify what you are adding, in this case COLUMN, as opposed to CONSTRAINT etc..
  18. W

    DDL to create TimeStamp field

    All of the following failed: CurrentDb.Execute "ALTER TABLE Audit ADD RecordCreatedDate DATE NOW() ;" CurrentDb.Execute "ALTER TABLE Audit ADD RecordCreatedDate SET DEFAULT NOW() ;" CurrentDb.Execute "ALTER TABLE Audit ADD RecordCreatedDate SET DEFAULT 'NOW()' ;" CurrentDb.Execute "ALTER...
  19. W

    DDL to create TimeStamp field

    Hi Guys I'm trying to use DDL to add a DATE field as above with NOW() as the default value.. I am using the same syntax pretty much (Altering instead of Creating a table), but its not working.. The error I get is: err.number = 3293 err.description = Syntax error in ALTER TABLE statement...
  20. W

    Create table DDL statement

    Hi Guys I'm trying to use DDL to add a DATE field as above with NOW() as the default value.. I am using the same syntax pretty much (Altering instead of Creating a table), but its not working.. The error I get is: err.number = 3293 err.description = Syntax error in ALTER TABLE statement...
Back
Top Bottom