Search results

  1. D

    FE version check

    and if the users and to shair the custom queries, reports, etc? tell them too bad!! or simply have them export/import between their private versions? -Mike
  2. D

    FE version check

    hm... like simply throwing up a pop up box that says, "You must update your client. Please exit and run G:\updates\UpdateFE.bat" Hm that would work. Another FE/BE situation I have is where I have 4 users. 3 of them frequently do their own queries/reports/etc. How can I still have multiple FE...
  3. D

    FE version check

    After my last thread I'm looking to split up all my databases in to a full FE and BE configuration. Someone suggested a way to automate a client upgrade, where I do a version check when the user starts the FE. Has anyone implemented something like this yet? I'm trying to think of a way that I...
  4. D

    the right way?

    Thanks Pat. Sorry I didn't realize that was the example. -Mike
  5. D

    the right way?

    What type of issues Pat? One of the other developers has done some development of code in 2002 and simply brought it in to 97 w/o a problem. When you state that I might want to start to "disambiguate" the objects. I'm assuming you mean by switching the forms over to bound forms instead...
  6. D

    Need Help Creating a Frequent Cust Combo Box

    If it is difficult to define your customers, I would use a CustomerID field in your customer table; and then bind that to your combo box. -Mike
  7. D

    the right way?

    Compact - nightly via a batch file. Repair - when needed - as a compact will fail over night, I'll know and then be able to repair the database the following day. -Mike
  8. D

    the right way?

    Yea I thought of doing something like that before Ken. The original reason I hesitated in doing that was if a user crashed while in "edit" mode, it would leave that record locked. Because the user base is all using Windows 98, we tend to see a lot of lock ups/crashes in just their OS. We do...
  9. D

    the right way?

    Good to know Pat. One other coworker that does development with me said she has no problem bringing home snippets of databases and working then in a Access XP environment. Pethaps it's simply that with the shear amount of code I have that something will most likely bomb out. I believe I've...
  10. D

    People names one or two fields?

    a little obvious, but I still do things wrong that are very obvious when someone else comments. if you store it just in one field how are you going to stort based on last name? You would cause more aggravation later on for yourself. I would encourage to split up information more often then not...
  11. D

    the right way?

    Sorry I'll try to clear it up. I apologize, I've been here for 3 years and I fully realize that how I pose my questions and the structure of my work is not standard; as the company itself is hardly standard. properties of the "EDIT" button and the code that's called Public Function...
  12. D

    Disable message pop-ups?

    docmd.SetWarnings and then either True(-1) or False (0) You can also disable it within a macro create a new macro Action: SetWarnings - Warnings On "No" Action: OpenQuery..... Action: SetWarnings - Warnings On "Yes" etc etc etc. -Mike
  13. D

    the right way?

    Hm... wow. well I've written a ton of code for nothing. If I can simply split the FE and the BE and have users not have any conflicts. I understand what Pat was suggesting. I'll just have to do a bit of research and thought in how I can overwrite a local copy of the FE and automate it as...
  14. D

    the right way?

    This seems like a very cumbersome way to potentially allow anywhere from 20-30 users to access data. So you have 20-30 identicle copies of a database pointing / Linked to one "data" (or backend) database. This opens up so many additional hurdles. In our sintuation, we have maybe 4 different...
  15. D

    the right way?

    Hi all, Neat forum, I'm glad I came across it. I've been working in Access databases for 5+ years now. At my current company for 3+ years. They are running on windows 98, using Access 97. They have multiple databases. Many of which have multiple users accessing them at the same time...
Back
Top Bottom