Search results

Now I see why you had qualms about structure. You would be much better off splitting the invoice into two tables: header and detail and and have customers and parts in separate tables also. There are scores of examples on the web how to set up invoicing in Access. You might want to google some...

I don't see anything wrong with the table structurally, on what you have shown. But would it not be simpler to create text fields for the parts and enter (or correct) their quantity directly rather than clicking them up and down by one? Just sayin'. Best, Jiri

This has nothing to do with with FE/BE. Splitting the database has nothing to do with concurrency issues. You split the databases to gain performance, not to avoid collisions. If you operate the same way all the time, you will see the same locking messages even after you split the database...

Sorry, pal, none of this makes any sense to me. I have never heard or seen anyone writing about Front End in an unsplit database, and the notion itself is bafflegab. In shared environments where the DB is not split users access all the resources in one file on the network. Code, queries, forms...

This is what Putin calls "polnyi chush"! First of all, splitting the database does not protect against collisions. Both users would be accessing the same back-end! Duh! Second, there is absolutely no "destructive interference" danger stemming from two or more people accessing the same same...

Hi, @split database - for two users on a home network, I would not bother splitting the db. Unless you want to customize the front end for your wife, the benefits of splitting are small (at a gigabit local network speed). @backups - mirroring disks is expensive and adds another point of...

I think the method takes two arguments, source and destination. I have read some people complaining it does not work for them. One condition is that the source file has to be closed and unlocked. At any rate, I presently use DBEngine.CompactDatabase and for safety reasons do the switching...

Thanks, Doc. I am sorry to hear you can't create a quick demo owing to IP issues. I was really looking forward to the proof of your pudding. :) Best, Jiri

Doc, it's always good to see other solutions especially solutions that work. Unfortunately, in this thread at least, most people are into theory which is for some of us hard to follow. A little working demo of what people actually propose would be appreciated, so we can compare real solutions...

Yes, you are right. I am using this code only on unsplit databases. I did not realize that the Application object here refers exclusively to the Front End object. I guess, one would need to open another Application object for the Back End and set the options there. Will play with it. Best, Jiri

@MushroomKing Hi there, It is not effective or wise to compact and repair on close every time by setting the "C&R on close" switch permanently. On the other hand I would not recommend keeping a big bloat of a file. You can set the limit on the size of the Back End and execute...

Dave, I entered the discussion here supporting your idea of using a bit-encoded flag. Of all the solutions offered here, I consider your original suggestion the most natural, effective and surely the fastest way to manage access to the buttons. I have provided a demo in post #33 showing...

Not quite true, Doc. Chuck has 17 users, each assigned a role. There are 131,072 possible roles that he can assign. :) Best, Jiri

Hi, the sub-table is a good idea but there should be a single variable per user (long integer if you are not planning to go over 32 reports, or a string) that manages the individual controls for him/her. The one-on-one method that you have contributes to the sluggishness of your code - you are...

Colin, the elementary problem with your approach is that you would have to hard-code the permissions in the form where the buttons are to be accessed. This means you would have to change the code every time a new user is introduced, or his permissions have been altered to add or remove a...

You admit that your example "is not based on user levels". But the problem is that the user wants just that: So, let's get to it Example: user 1 - can access reports no.: 1-3-7-10-12-16 user 2 -...

Colin, I have no idea what you are doing. You are being asked to set the visibility of command buttons based on user's access level and do it in the most efficient way possible. So, in my understanding you need some control mechanism whereby you set the visibility of the buttons for a...

Colin, I am not familiar with an Access function "ShowControls". Or is that something you have created, and if so, would you like to show us what it is before arguing its merits? Thx. Best, Jiri

I have read the OP and consider the following the gist of the matter: As I pointed out most likely the reason (or the main reason) the processing is slow is that you have to vary the [ControlAuto] variable outside the sub and engage the dlookup test code seventeen times, making sixteen...

Yeah, the OP code is strange in that it controls 17 switches by a value of single variable (or field). So where is the [ControlAuto] value set ? It cannot carry both the value of 10 and 11 on a single pass through the sub. That means that the routine is called 17 times to pick a single value...